When i startup terminal a window opens and all it says is "[Process completed]". I dont know that i switched anything and i cant get in even if i did, I was hopping someone would know what this error meant. I looked threw the inspector and opened new windows with no avail. It worked yesterday!? Any help would be appreciated!
Terminal app quit working [Process completed]
- Thread starter bfc
- Start date
That just happened to me too. The terminal also says "Process was terminated by signal 11" I can't ssh to my machine anymore either. "Top" will run from the cpu monitor, but if you control-c that it will give process completed again.
Well....I just got it back. I had made a folder called "init" in my Library folder to try some new personal terminal settings, and I just removed it, and now my tcsh works fine. and my ssh works fine. put it back in and it broke. I was trying to use psuedo instructions in /usr/share/init/tcsh/README which sounded like a unix/osx hack to personalize tcsh. Maybe there are some files in that directory that are the culprit if everything else seems to be working. I'd like to know what the "signal" messages mean in the shell.
Well....I just got it back. I had made a folder called "init" in my Library folder to try some new personal terminal settings, and I just removed it, and now my tcsh works fine. and my ssh works fine. put it back in and it broke. I was trying to use psuedo instructions in /usr/share/init/tcsh/README which sounded like a unix/osx hack to personalize tcsh. Maybe there are some files in that directory that are the culprit if everything else seems to be working. I'd like to know what the "signal" messages mean in the shell.
Well, I'm looking at those corresponding files on my machine and nothing in those directories is being changed by root on a regular basis. The way they're set up now, only root can change them. I suppose all those files were changed to mode 777 and all the data, save the filenames, destroyed by root on Sept 25, at 5:39 and 3 minutes after at 5:42. The timing somehow makes me think it's a shutdown realted issue... My question would be what could root have possibly done, or wanted to do that caused that? It can't have happened too many days after you installed beta, so is it right to assume that the rest of us have a time bomb on our machines that's about to kill our terminals and all those commands as well? I want to think of some preventative action to take.
I noticed root did change my ssh prng_seed file mode to 750, and ssh wanted it to be at 600. I don't know what caused that either.
I noticed root did change my ssh prng_seed file mode to 750, and ssh wanted it to be at 600. I don't know what caused that either.
avalenz
Registered
I just suffered the same problem. Deleted the init folder like you said and sure enough, that fixed my problem. However, I still wanted to use customized aliases file (and I do at work so I knew it was possible) so I quickly figured out that it was the aliases file that ResExcellence has you copy over from /usr/share/init/tcsh/ that causes the signal 11 problem. Since they have you delete that entire file anyway, simply create a new file in that directory without copying that other one and you should be fine.
-Ali