Your message dated Sat, 14 Nov 2009 12:33:51 +0900
with message-id <[email protected]>
and subject line upgrading from pre-3.1.9 no longer supported
has caused the Debian Bug report #385159,
regarding Erroneous 'permission to use at denied'
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.)
--
385159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385159
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: at
Version: 3.1.8-11
Severity: important
This seems to illustrate an erroueous 'permmission denied to use at'
response:
cn2:/etc# cat at.deny
alias
bin
daemon
ftp
games
gnats
guest
irc
lp
mail
man
nobody
proxy
qmaild
qmaill
qmailp
qmailq
qmailr
qmails
sync
sys
www-data
cn2:/etc# ls -la at*
-rw------- 1 root root 128 Aug 23 09:52 at.deny
cn2:/etc# su - amanda
ama...@cn2:~$ id
uid=1001(amanda) gid=6(disk)
groups=6(disk),34(backup),37(operator),103(webadmin)
ama...@cn2:~$ echo '123' | at now
You do not have permission to use at.
ama...@cn2:~$
According to the documentation, if there's no /etc/at.allow, and the
user's name isn't in /etc/at.deny, the user should be allowed to use
'at.'
Thanks for looking into this.
-Kevin Zembower
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages at depends on:
ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an
ii qmail-run [mail-trans 1.1.0 sets up qmail as mail-transfer-age
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
as even oldstable has at/3.1.10 and this problem should only occur when
upgrading from a version older than 3.1.9, this bug should no longer be
relevant. I'm thus closing the report.
If there are still issues remaining, please reopen the bug.
Regards,
Ansgar
--- End Message ---
