tag 437180 confirmed pending
thanks
Wolf Wiegand wrote:
> Hi Christian,
>
> Christian Kastner wrote:
>
>>> $ crontab -l
>>> @reboot FOO=$(ls /); echo $FOO | mail w...@localdomain
>>> @reboot FOO="asdf"; echo $FOO | mail w...@localdomain
>>>
>>> $ grep CRON /var/log/syslog | egrep "wolf|reboot"
Hi Christian,
Christian Kastner wrote:
> > $ crontab -l
> > @reboot FOO=$(ls /); echo $FOO | mail w...@localdomain
> > @reboot FOO="asdf"; echo $FOO | mail w...@localdomain
> >
> > $ grep CRON /var/log/syslog | egrep "wolf|reboot"
> > Mar 8 11:35:10 denkbrett /usr/sbin/cron[2766]: (CRON) INFO (
Hi Wolf,
Wolf Wiegand wrote:
> Justin Pryzby wrote:
>
>> Could you test if this problem exists with recent versions of cron?
>
> I just checked on a current sid machine, the problem still exists:
>
> $ dpkg -l cron | grep ^ii
> ii cron 3.0pl1-103 management of regular backgr
Package: cron
Version: 3.0pl1-100
Severity: normal
Hi,
I just discovered the following behaviour with cron which seems like a
bug to me. A user has the following entries in his personal crontab
(lines abbreviated):
30 01 * * * CAL=`calendar`; [ ! -z "$CAL" ] && calendar | mail [...]
30 01 *
4 matches
Mail list logo