Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 265030 - sys-process/at-3.1.10.2-r1 can't run job at specified time
Summary: sys-process/at-3.1.10.2-r1 can't run job at specified time
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Cron Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-05 22:45 UTC by NiTr0
Modified: 2009-04-06 18:53 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description NiTr0 2009-04-05 22:45:10 UTC
I tried it run reboot at 5AM, so I create file "reboot" and put in it one line "reboot"; then run "sudo at 5AM -f reboot". At morning I saw in syslog line:
Apr  4 05:00:00 [atd] Job        1 a00001013b0bb8 - groupid 0 does not match file gid 25
But directory /var/spool/at/atjobs was empty.
I query again job - and saw in this directory file, that is owned by root and has attributes 700.
Comment 1 Thilo Bangert (RETIRED) (RETIRED) gentoo-dev 2009-04-06 18:53:13 UTC
it looks to me, at is refusing to run the command because the file in which you put it hast the wrong permissions.

is that correct?
if yes, then there is no bug. that is how at is supposed to work. its a security feature, i suppose...

try 
$  echo 'reboot' | sudo at 5AM

or make sure the file 'reboot' is owned by root.