From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Re: cvsimport in cron
Date: Tue, 27 May 2008 13:08:45 +0200 [thread overview]
Message-ID: <g1gq3u$jb$1@ger.gmane.org> (raw)
In-Reply-To: <ce7555260805270345x353cfc76ja3f7ec83a0ab5c61@mail.gmail.com>
Barra Mac Mathúna venit, vidit, dixit 27.05.2008 12:45:
> 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
next prev parent reply other threads:[~2008-05-27 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 18:00 cvsimport in cron barrymac
2008-05-26 23:13 ` Martin Langhoff
2008-05-27 10:45 ` Barra Mac Mathúna
2008-05-27 11:08 ` Michael J Gruber [this message]
2008-05-27 11:31 ` Martin Langhoff
2008-05-27 13:33 ` John J. Franey
2008-05-27 15:31 ` Barra Mac Mathúna
2008-05-27 12:08 ` Barra Mac Mathúna
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='g1gq3u$jb$1@ger.gmane.org' \
--to=michaeljgruber+gmane@fastmail.fm \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).