kubuntu-users Digest, Vol 15, Issue 39
C Hamel
yogich at sc2000.net
Fri Apr 14 15:10:20 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 14 April 2006 06:00, kubuntu-users-request at lists.ubuntu.com wrote:
> Message: 1
> Date: Thu, 13 Apr 2006 13:22:55 +0200
> From: Simon Zilliken <simon.zn at online.de>
> Subject: Re: user cronjobs are not performed
> To: Kubuntu Help and User Discussions <kubuntu-users at lists.ubuntu.com>
> Message-ID: <200604131322.55821.simon.zn at online.de>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Am Donnerstag 13 April 2006 12:07 schrieb NetSKaVeN:
> >HEll-o!
> >
> >El Jueves 13 Abril 2006 11:37, Simon Zilliken escribió:
> > > Apr 13 11:25:01 localhost /USR/SBIN/CRON[4897]: (simon) CMD (nice
> > > clamscan -rl /home/$USER/Desktop/clamscan.daily /home >& /dev/null)
> >
> >it sounds as a PATH problem. Try to use absolute path in all commands
> >into cron jobs
>
> Thanks, but I got the same effect. The command appears in syslog, but
> nothing is happening. My crontab looks like this:
>
> SHELL=/bin/bash
> PATH=/usr/local/bin:/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/
>X11
>
> # scan /home for viruses daily
> 0 18 * * * nice clamscan -rl /home/$USER/Desktop/clamscan.daily /home
>
> >& /dev/null
>
> # eof
>
> (of course I change the time for testing)
>
> More ideas?
>
>
I had that same problem on Breezy --now Flight6-- so got rid of the culprit &
installed syslog-ng, instead. Since then, everything works.
- --
...CH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEP7tf6n1LutVYpQARAjZsAJ9aHquOcxufQ4OthqhqBXBIKT/txwCaAnqE
bwf74xh3Eu+Bxbk1EiFlzzA=
=amFf
-----END PGP SIGNATURE-----
More information about the kubuntu-users
mailing list