Your message dated Mon, 25 Mar 2013 11:56:57 +0100 with message-id <[email protected]> and subject line Re: Bug#703882: at not usable as regular (non-root) user has caused the Debian Bug report #703882, regarding at not usable as regular (non-root) user to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 703882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703882 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: at Version: 3.1.13-2 Severity: important Dear Maintainer, 'at' currently is not usable as a regular user contradicting the man page. In the regular installation, only /etc/at.deny exists and thus from the man page a user not listed in that file should be able to use at (my user is not listed there). Currently, this does not work however: bash[2]$ atq You do not have permission to use atq. bash[2]$ I started debugging at and it turns out that 'at' cannot even read /etc/at.deny and thus concludes that no user except root should be allowed to use it (seen easily also in strace): bash[2]$ strace -e open atq open("/etc/ld.so.cache", O_RDONLY) = 4 open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY) = 4 open("/etc/nsswitch.conf", O_RDONLY) = 4 open("/etc/ld.so.cache", O_RDONLY) = 4 open("/lib/x86_64-linux-gnu/libnss_compat.so.2", O_RDONLY) = 4 open("/lib/x86_64-linux-gnu/libnsl.so.1", O_RDONLY) = 4 open("/etc/ld.so.cache", O_RDONLY) = 4 open("/lib/x86_64-linux-gnu/libnss_nis.so.2", O_RDONLY) = 4 open("/lib/x86_64-linux-gnu/libnss_files.so.2", O_RDONLY) = 4 open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 4 open("/etc/group", O_RDONLY|O_CLOEXEC) = 4 open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 4 open("/etc/at.allow", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/at.deny", O_RDONLY) = -1 EACCES (Permission denied) You do not have permission to use atq. bash[2]$ The installed rights confirm this: bash[2]$ ls -l /etc/at.deny -rw-r-----. 1 root bin 144 Nov 30 2009 /etc/at.deny bash[2]$ As a quick test, I added read rights for all other users, but also with no success: bash[2]$ sudo chmod o+r /etc/at.deny bash[2]$ atq Cannot change to /var/spool/cron/atjobs: Permission denied bash[2]$ At this point I stop as I'm not sure how this is supposed to work in the first place. I would really appreciate if we can fix things up. Let me know if I can test something. Thanks Detlev -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages at depends on: ii libc6 2.13-37 ii libpam-runtime 1.1.3-7.1 ii libpam0g 1.1.3-7.1 ii lsb-base 4.1+Debian8 Versions of packages at recommends: ii exim4-daemon-light [mail-transport-agent] 4.80-7 at suggests no packages. -- Configuration Files: /etc/at.deny [Errno 13] Permission denied: u'/etc/at.deny' -- no debconf information
--- End Message ---
--- Begin Message ---On 03/25/2013 11:51, Detlev Zundel wrote: > Ah, your indication that there maybe consistency issues prompted me to > purge and reinstall 'at' and everything now works for me. Unfortunately > this also means that I do not know where the original problems came from > but very likely this would have been very hard to reconstruct anyway. > > So thanks for the quick help and please go ahead and close the bug. Done. Ansgar
--- End Message ---
