> > > When you readded yourself, did you specify the old > > user id using the -u > > flag to useradd? > > Well, no I didn't, I just copied the files over and > went for it. Looks like that approach won't work > though. So now it seems that all that is left is > remaking all the user and group accounts by hand. ugh. > Thats what I'm gonna do after i finish this email. > > On a side note though, i added a completely new user > to test the system out. Even that account gave me the > same errors. Seems mandrake doesn't like the idea of a > fresh system with an already populated home directory, > yech, kinda defeats the purpose of having seperate > partitions. If my experience is any indicator, if you > want to avoid massive errors, you gotta reformat all > your partitions and then manually readd your users by > hand, and *then* sync the directories from backup > copies to make it work. Kind of sick actually, if I'm > right and that statement is true, what the hell am I > going to do when I have 3,000 users on this system and > it needs a fresh install for whatever reason? Maybe > mandrake isn't the best option for a server *shrug* > Shouldn't there be an easier way to recover > users/groups/directories in the event of a failure? > > Ken
Surely there's an easier way than this. For one thing, seems that I remember an old command that would automatically check system related files for proper ownerships and access. It was "setperms", or "chkperms", or something like that. But that was a looong time ago...on an SCO system, no less. Perhaps there is a comparable utility in existence today. I couldn't find any binaries similar to the above names on this LM81 system, unfortunately. I would think that this problem has been addressed by someone, somewhere. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
