Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '"Process Completed" strikes again!' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
"Process Completed" strikes again!
Authored by: Chas on Dec 04, '01 08:18:17PM

I've just encountered this bug again, on my Powerbook G3/500 running 10.1.1. And the darn thing is, I've seen this bug before, and somehow I fixed it, but I can't remember how.
I tried the trick of running a command from the menu in Terminal.app, but that doesn't work for me, it did nothing, didn't run the command, just echoed it. I tried copying another copy of /bin/tcsh from a working system on another machine (as root of course) and now I don't get the "Process Completed" message, I get "[Process exited - exit code 1]" so it appears something is deeply hosed. Could just be a permission problems, now I've got to find a way to do chmod and chown from a GUI app.
I noted that when this bug appeared, at first when I launched Terminal, I got the welcome message, then I never got a prompt, it just hung while the CPU monitor went up to 100%. So I logged out, relogged in and then it started giving the Process Completed message.
So if any of these symptoms sound familiar, let me know. I've started manually backing up everything and it looks like I'm going to have to reformat and reinstall, but if there's a way to repair this without major disruption, I'd sure like to hear it. Darn it, I just got Fink and Gnome 1.4, PhP/MySql/Apache, and VPC all working optimally, and now I've got to erase the system do it all over again!



[ Reply to This | # ]
diagnostics
Authored by: babbage on Dec 04, '01 11:05:58PM
You're definitely getting the same error that people were talking about a year ago? The file /bin/tcsh has a zero file length? On my system, the /bin directory has four *sh files: csh, sh, tcsh, zsh. All of them have the same time stamp, corresponding to the day I installed the OS. Are you seeing the same timestamp for each file (assuming you can get that far), or if not is tcsh newer perchance? If so, that might point to the date where things went wrong, and that in turn might help you piece together how the shell got hosed.

One method of low level desperation would be to login as ">console" at the login screen. If you're lucky this will try to log you in with whatever shell is available, if you can't set your preferred shell to one of whichever ones remain for you. Similarly, you might be able to get in via "single user mode" -- boot while holding down shift-S (I think, haven't had a reason to use it yet but I think that's right), and this should dump you in as root & hopefully running under /bin/sh.

If you can get to a prompt somehow, and you have some kind of /bin/tcsh file present, you need to analyze it a bit. Try running "file /bin/tcsh", which should tell you "/bin/tcsh: Mach-O executable ppc". If you get nothing, or something else, then the tcsh you installed isn't valid. Copying over a copy from the install disc seems like a good idea, but I've never been through this so...

Let us know more & we can keep trying to help...

[ Reply to This | # ]