Stephen Liu wrote these words on 12/29/05 10:01 CST: > Any advise? OR can any folk on the List shed me some light. TIA
I'm not sure I know what your problem is, however, I should have spoke up earlier with this tidbit. I suppose this is why I didn't respond earlier, because what I'm about to say I thought everyone knew. But upon reflection, I can see this isn't something that is common knowledge. Anyway, in your original message you said you had a group.lock file that you renamed (or something like that). I'm not sure why you renamed it (if that is what you did), but I do remember your original message had something to do with the group.lock file. /etc/group.lock is created when the root user runs the vigr program. Likewise /etc/passwd.lock is created when you run the vipw program. So best as I can tell, you were running the vigr program and then somehow exited uncleanly from it (I am totally guessing here) leaving the file on disk. I'm not sure what happens at that point, however I just wanted to point out about the group.lock file is created by the vigr program. I don't remember anyone pointed this out, in fact, nobody could explain the file. This was just an effort to explain the file. If you'll explain what exactly is wrong (please summarize, sometimes you messages are so long that I lose train of thought trying to read them), we'll all see if we can help. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 10:09:00 up 95 days, 19:33, 3 users, load average: 0.99, 0.82, 0.44 -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
