On Tue, Nov 8, 2011 at 15:33, Bob Proulx wrote:
> The nscd is not required for cron jobs to run. I don't want to
> suggest that you thrash your production machine but if you could test
> this on a test machine I think you will find that nscd is not required
> for cron. Really it isn't! I assur
> You can append "2>&1 >> /var/log/nightly-git.log" to get the output
> logged to a file.
Those redirections are the wrong way round. Only standard output is
redirected to the file.
To redirect both standard output and standard error you need to append
">> /var/log/nightly-git.log 2>&1"
--
Chee
Adam Mercer wrote:
> Bob Proulx wrote:
> >> from this I was able to determine that NSCD wasn't running, restarting
> >> this allowed jobs to run successfully!
> >
> > Does this mean that you are running NIS/YP or LDAP from the network?
> > Are your servers "slow" such as on a remote network or othe
On Tue, Nov 8, 2011 at 12:21, Bob Proulx wrote:
>> from this I was able to determine that NSCD wasn't running, restarting
>> this allowed jobs to run successfully!
>
> Does this mean that you are running NIS/YP or LDAP from the network?
> Are your servers "slow" such as on a remote network or oth
Adam Mercer wrote:
> Nov 8 10:48:01 bull /usr/sbin/cron[1123]: (laltest) ORPHAN (no passwd entry)
>
> from this I was able to determine that NSCD wasn't running, restarting
> this allowed jobs to run successfully!
Does this mean that you are running NIS/YP or LDAP from the network?
Are your serv
On Tue, 08 Nov 2011 10:44:58 -0600, Adam Mercer wrote:
> On Tue, Nov 8, 2011 at 10:25, Camaleón wrote:
>
>> Do a "grep -i cron /var/log/syslog" and check for the output.
(...)
> and then the previous:
No trace, it seems not to be triggered at all.
>> I don't know why is failing, though the m
On Tue, Nov 8, 2011 at 10:44, Adam Mercer wrote:
>> You can append "2>&1 >> /var/log/nightly-git.log" to get the output
>> logged to a file.
>
> That's I'll see if that gives any more information.
I created another entry in the crontab with the logging enabled for a
few minutes in the future and
On Tue, Nov 8, 2011 at 10:25, Camaleón wrote:
> Do a "grep -i cron /var/log/syslog" and check for the output.
# grep -i cron /var/log/syslog
Nov 8 07:17:01 bull /USR/SBIN/CRON[6222]: (root) CMD ( cd / &&
run-parts --report /etc/cron.hourly)
Nov 8 07:49:05 bull crontab[6280]: (laltest) LIST (
On Tue, 08 Nov 2011 07:52:33 -0600, Adam Mercer wrote:
> On a squeeze box I'd like to run a script every night at 1:01am, as such
> I have the following entry in my crontab:
>
> $ crontab -l
> 1 1 * * * /home/laltest/test/nightly/nightly-git.sh
> $
>
> However the script never runs and I d
9 matches
Mail list logo
