On Wednesday 21 March 2001 01:40, you wrote:
I was just a bit quick with the fingers.
Sometimes you gotta watch those fingers... ;-)
I noticed I had made a mistake and I killed yast. I thought I killed it before any scripts ran.
Better to let it finish, then restart it and *then* make changes... (Easy enough for me to say... Not putting you down ,though - been there, done that ;-) It's just not always possible to know how far YaST has gotten in it's course of actions...
"another suse config is running. waiting for it to finish......."
Which probably prevents some fatal shit from happening...
I checked 'ps ax' and it was true. the thing was still running. I killed it and then closed my other yast session.
Maybe this is where things got bad? e.g. if SuSEconfig was in the process of writing resolv.conf, and didn't get to finish?
...and tried to commit but it won't start suseconfig in yast anymore.
I tried to hand start suseconfig but it won't start anymore saying it detected a running copy even though there is none.
Starting by hand/from YaST doesn't make much difference in this case (I think), but IIRC a lock-file is made whenever SuSEconfig and/or similar stuff runs. This is to make sure only ONE instance runs at a time. Which basically makes a lot of sense... (Imagine the inconsistencies that could arise if two SuSEconfigs were changing the system simultaneously, one changing the settings that the other one's using as a basis for something else...) So what you might try is: (with no *new* instances of yast and suseconfig running) look for a file called 'lock' in /var/some/directory or perhaps /proc/some/other/directory most likely the path involves yast or suseconfig or similar. Once (if) you find it, and you have made _sure_ ps ax doesn't show suseconfig (or yast) - delete it (the lock-file that is) then try running SuSEconfig and see what happens... I'm not at all certain of what I'm saying here, though. But I do seem to remember this scenario from somewhere, and this course of action... Maybe something I read on SDB? This was back when I was using 6.4 though, and since I've just recently shifted to 7.1 (skipping 7.0) I'm not entirely sure how things look for you, or if this has changed since 6.4... Anyone? In any case: BE CAREFUL
I know this is all my fault...
Yeah well - since I abandoned Wintendo, at least I know that it's MY FAULT, and not some 'feature'... Hope I helped, and cheer up :-) Jon
_________________________________________________________________ WHY Get your FREE download of MSN Explorer at http://explorer.msn.com when you got Konqueror?