On Tue, Jun 27, 2006 at 11:23:09PM +0200, martin f krafft wrote:
> > % ls -l =maildrop =lockmail.maildrop
> > -rwxr-sr-x 1 root mail 10368 2004-08-20 00:40 /usr/bin/lockmail.maildrop
> > -rwxr-sr-x 1 root mail 157384 2004-08-20 00:40 /usr/bin/maildrop
>
> seamus:~> ls -l =maildrop =lockmail.maildrop
> -rwxr-sr-x 1 root mail 10472 2005-08-27 22:07
> /usr/bin/lockmail.maildrop*
> -rwxr-sr-x 1 root mail 149032 2005-08-27 22:07 /usr/bin/maildrop*
>
> Why it still cannot write to /var/mail (despite that it *should*
> *not*, "I have absolutely no idea". :)
Well, mine does.
% grep "^File: $MAIL" .mail.log* -c
.mail.log:5701
.mail.log.2k3:1490
.mail.log.2k4:5894
.mail.log.2k5:7696
% ls -ld /var/mail
drwxrwsr-x 2 root mail 4096 2006-06-27 22:32 /var/mail
As you can see, it has been doing so successfully for years now, and rather
repetitively. That is why I have difficulty trying to believe that this is
a maildrop bug.
Do you also use something like SELinux which could perhaps revoke these
privileges? What does "update-alternatives --display lockmail" do on your
system, maybe it got broken somehow?
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
