git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: barrymac <barrymac@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: cvsimport in cron
Date: Tue, 27 May 2008 11:13:34 +1200	[thread overview]
Message-ID: <46a038f90805261613v4ad72ddcxe6ee78fa0b54f89e@mail.gmail.com> (raw)
In-Reply-To: <17476529.post@talk.nabble.com>

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

  reply	other threads:[~2008-05-26 23:14 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 [this message]
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

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=46a038f90805261613v4ad72ddcxe6ee78fa0b54f89e@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=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).