> When I went from 2.1.42 to 2.1.46, MH (the one true mail system) stopped
> working for me. It seems that I am no longer able to "inc" my mail out of
> the mail spool, which is a (NFS-mounted) Solaris-served, t-bit mail
> directory. Strace shows the following happening:
>
> [...]
> stat("/var/spool/mail/,LCK.a01595", 0xbfffdea8) =
> -1 ENOENT (No such file or directory)
> unlink("/var/spool/mail/,LCK.a01595") =
> -1 ENOENT (No such file or directory)
> creat("/var/spool/mail/,LCK.a01595", 0400) = -1 EACCES (Permission denied)
> [...]
>
> The interesting thing is that, after this sequence of events, the funky LCK
> file it wants to create does, in fact exist. Since the ENOENT errors above
> make it clear that the did not exist before, I conclude that the creat()
> worked, but then returned an incorrect error code.
>
> Anybody else seen anything like this? Like I said, 2.1.42 didn't do this
> to me...
i've had similar circumstances with files created by initializing daemons
such as syslogd and inetd. really bizarre things occur if /tmp
is a link which points to /var/adm. migrations into the permanent
directory structure don't seem to be succeeding in some cases.
more disturbing is the appearance of some corruption on my backups.
whether the two are related i can't say.
namei and conditional calls to dcache suggest to me this may be
permission related.
i'll look a little further and post you.
bill