[ale] weird error(2.0.0 upgrade saga)

[Michael David Ivey]

I checked Doc/Changes, and found nothing like this.  I get this error 
when I send a message to majordomo or a majordomo list (on my machine).

cannot lockf(/etc/aliases.dir, fd=3, type=1, omode=37777777777, euid=0): 
Device or resource busy
cannot lockf(/etc/aliases.dir, fd=3, type=10, omode=37777777777, euid=0): 
Device or resource busy
cannot lockf(/etc/aliases.dir, fd=3, type=1, omode=37777777777, euid=0): 
Device or resource busy
cannot lockf(/etc/aliases.dir, fd=3, type=10, omode=37777777777, euid=0): 
Device or resource busy
cannot lockf(/etc/aliases.dir, fd=3, type=1, omode=37777777777, euid=0): 
Device or resource busy
cannot lockf(/etc/aliases.dir, fd=3, type=10, omode=37777777777, euid=0): 
Device or resource busy


Anyone seen this?  Any suggestions?  

Also, I'm thinking that maybe it has to do with init, the one thing I 
haven't taken to the bleeding edge yet.  =)

So, my question is, has anyone upgraded init yet?  Did you boot from 
floppy to do so, or just drop it in?  I'm hesitant to just replace init 
while the system is up.

Thanks.


 
Michael Ivey, Director of Computer Operations   |  ivey at gsu.edu
Georgia State Television                        |  http://gstv.gsu.edu/~ivey
                            
Key to UNIX:
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'