git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Barra Mac Mathúna" <barrymac@gmail.com>
To: git@vger.kernel.org
Subject: Re: cvsimport in cron
Date: Tue, 27 May 2008 12:08:02 +0000	[thread overview]
Message-ID: <ce7555260805270508g6ea72ee5hd0cc49b716698cbe@mail.gmail.com> (raw)
In-Reply-To: <ce7555260805270345x353cfc76ja3f7ec83a0ab5c61@mail.gmail.com>

I've also tried the command like this:

git-cvsimport p --no-cvs-direct -vio master CVSMODULE

Apparently cvsps has it's own client implementation, so I thought I'd
disable that in order to be more sure that it was working in the same
way as the normal cvs over ssh update that works fine in cron.

Barry.


On Tue, May 27, 2008 at 10:45 AM, Barra Mac Mathúna <barrymac@gmail.com> wrote:
> 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?
>
> I also downgraded to the stable version according to gentoo, so I'm on
> using 1.5.3.7 now, same result. Unfortunately I might have to give up
> soon and ask developers to update their own repositories, as it's
> burning up time.
>
> Will post of course if I find the solution.
>
> Thanks,
> Barry.
>
>
> On Tue, May 27, 2008 at 12:13 AM, Martin Langhoff
> <martin.langhoff@gmail.com> wrote:
>> On Tue, May 27, 2008 at 6:00 AM, barrymac <barrymac@gmail.com> wrote:
>>> Apologies if this is a standard mistake, I'm not very experienced with cron.
>>> I'm trying to run cvsimport commands from within a cron job but it always
>>> returns:
>>
>> I've done this plenty, so it's known to work. Not sure why it's
>> failing in your case.
>>
>>> I use ssh keys and have tested that they work  by using scp within the
>>> script. The script goes as follows:
>>
>> That's a good start. Have you tried a cvs-over-ssh cvs operation from cron?
>>
>>> It would also be nice if someone could tell me also how to log the output.
>>
>> Just wrap the commandline in
>>
>>  ( $cmd 2>&1) > /tmp/cvsimport.log
>>
>> HTH, and tell us what the problem was - so the next one to bump into
>> it find the answer in the list ;-)
>>
>> cheers,
>>
>>
>>
>> m
>> --
>>  martin.langhoff@gmail.com
>>  martin@laptop.org -- School Server Architect
>>  - ask interesting questions
>>  - don't get distracted with shiny stuff - working code first
>>  - http://wiki.laptop.org/go/User:Martinlanghoff
>>
>
>
>
> --
> I must Create a System, or be enslaved by another Man's
> Wm. Blake 1757 - 1827
>



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

      parent reply	other threads:[~2008-05-27 12: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
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 [this message]

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=ce7555260805270508g6ea72ee5hd0cc49b716698cbe@mail.gmail.com \
    --to=barrymac@gmail.com \
    --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).