Re: cvsimport in cron

["Barra Mac Mathúna" <barrymac@gmail.com>]

Wow thanks so much!!

It's great to get such a quality response from the mailing list!

On to the next problem :-)


On Tue, May 27, 2008 at 1:33 PM, John J. Franey <jjfraney@gmail.com> wrote:
> On Tue, 2008-05-27 at 13:08 +0200, Michael J Gruber wrote:
>> 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
>>
>
> Great suggestion!
>
> I am also having this problem.  To debug, I inserted env as you
> suggested.  (Doh, why didn't this occur to me weeks ago?).  I compared
> the output of cron and login-shell runs.
>
> So what is the critical env diff between cron run and login run?
>
> The answer is:  CVS_RSH=ssh
>
> Be sure to export.
>
> Thanks.
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>



-- 
I must Create a System, or be enslaved by another Man's
Wm. Blake 1757 - 1827