git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: cvsimport in cron

From
Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
Date
May 27, 2008, 11:08 UTC
Message-ID
<g1gq3u$jb$1@ger.gmane.org>
In-Reply-To
<ce7555260805270345x353cfc76ja3f7ec83a0ab5c61@mail.gmail.com>
Barra Mac Mathúna venit, vidit, dixit 27.05.2008 12:45:
Show 12 quoted lines
> Thanks Martin,
> 
> Nice to know how to log the progress! Good tip to try normal cvs over
> ssh, which works fine.
> 
> I wish it was possible to get more verbose output from the git
> cvsimport command. The connection refused error seems to me to be
> misleading. I would expect at least some output from cvsps but it
> doesn't even get to the first step.
> 
> So if everything works at the command line, what significant things
> can be different in a cron job?

The environment! Put "env" in your cron job and compare the output to "env" on the command line. cvs or cvsps may be in $PATH on the command line but not in cron, or $PERL5LIB might be different.

Cheers, Michael

Previous: Barra Mac MathúnaNext: Martin Langhoff
Message 4 of 8 in “cvsimport in cron”
  1. barrymacMay 26, 2008
  2. Martin LanghoffMay 26, 2008
  3. Barra Mac MathúnaMay 27, 2008
  4. Michael J GruberMay 27, 2008
  5. Martin LanghoffMay 27, 2008
  6. John J. FraneyMay 27, 2008
  7. Barra Mac MathúnaMay 27, 2008
  8. Barra Mac MathúnaMay 27, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.