From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problems running doxygen from cron
Date: Sat, 14 Feb 2009 16:22:50 +0100 [thread overview]
Message-ID: <200902141622.55119.wonko@wonkology.org> (raw)
In-Reply-To: <79e3aefb0901142236l57797c02q15ec68291c68d74f@mail.gmail.com>
Dirk Uys wrote:
> I have a problem when running doxygen from a cron job. It seems like
> doxygen is simply aborting at an arbitrary point during execution. I
> tried to search on the internet, but could not find anything similar
> reported.
[...]
> My cron entry is
> 45 * * * * /home/user/script.sh >> /home/user/debug.log
I would add a " 2>&1" to the cron entry in order to get stderr output
logged, too. Maybe there are error messages you are missing.
My cron problems usually come from the PATH being restricted, anthough
this shoudl not matter in your case with the script, I think. Anyway, I'd
start it with "#!/bin/bash -l" in order to open a login shell, and I
would include the "env" command in the script so I can spot differences
in the environment.
Just some ideas,
Wonko
next prev parent reply other threads:[~2009-02-14 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 6:36 [gentoo-user] problems running doxygen from cron Dirk Uys
2009-02-14 15:22 ` Alex Schuster [this message]
2009-02-16 6:40 ` Dirk Uys
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=200902141622.55119.wonko@wonkology.org \
--to=wonko@wonkology.org \
--cc=gentoo-user@lists.gentoo.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