Package 'at' is broken

Bug #113988 reported by Christian Andretzky
2
Affects Status Importance Assigned to Milestone
at (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: at

simply try to create a at-job. The job is created and placed into the at-queue. But the job is never executed. After a unknown time the job is automatically removed from the queue.
I saw this problem on feisty (7.04) and edgy (6.10) too.
With this problem the system is completely unuseable because some of our maintenance (security) tasks require this feature.

Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

Here's a simple test. Can you try it please. at(1) is working for some of us so we need to find out why your experience differs.

$ echo touch /tmp/created_by_at | at now
warning: commands will be executed using /bin/sh
job 3787 at 2007-08-13 11:45
$ ls -l /tmp/created_by_at
-rw-r--r-- 1 ralph ralph 0 2007-08-13 11:45 /tmp/created_by_at
$

Revision history for this message
Christian Andretzky (christian-andretzky-mb) wrote :

Ooops - because there was no reaction for the lon time I forgot to close this bug - sorry.
The reason for my problem was located in a wrong description how to integrate the pam-logindevperm package into the system.
In the description I found in the web, it was suggested to include/append the line 'session required pam_devperm.so' to /etc/pam.d/common-session.

Never do this. The suggested line instead has to included directly to the _really_ involved files: /etc/pam.d/{gdm|kdm|login} for example.

If the line 'session required pam_devperm.so' is located in common-session the cron utility will no longer work, because common-session is also included in /etc/pam.d/cron and the authentication fails.

Sorry again for the false alarm.

Revision history for this message
Daniel Hahler (blueyed) wrote :

Closing as Invalid, as per reporter's comment.
Thank you for reporting back.

Changed in at:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.