Hi,
On 04/25/2010 09:44 PM, Christian Kastner wrote:
Fahad Ahmad wrote:
I am facing the exact same problem as the original poster on all my
debian lenny servers. The servers that are still on etch with the exact
same pam configurations have no problems running jobs
as normal users.
Here
Fahad Ahmad wrote:
I am facing the exact same problem as the original poster on all my
debian lenny servers. The servers that are still on etch with the exact
same pam configurations have no problems running jobs
as normal users.
Here is the strace output from cron:
*snip*
443
What is it that cron is writing to syslog? Something about
permission denied
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Mon, Jul 30, 2007 at 07:07:38PM +0200, Mattia Monga wrote:
Package: cron
Version: 3.0pl1-100
Severity: important
A very simple user crontab is never executed
$ crontab -u monga -l
# m h dom mon dow command
* * * * * date /tmp/date.user
This really looks like a PAM configuration
Package: cron
Version: 3.0pl1-100
Severity: important
A very simple user crontab is never executed
$ crontab -u monga -l
# m h dom mon dow command
* * * * * date /tmp/date.user
#
However, an analogous root crontab works!
# crontab -u root -l
# m h dom mon dow command
* * * * * date
5 matches
Mail list logo
