Kill old CLI processes?

[Zombie13]

Hi there!

Very noob question, but I can't find the answer via Google...

When I start a new shell in Workbench 3.1, the new window says "New Shell process 3" before giving me a "3.Workbench:>" prompt. How do I go about killing process 1 & 2, so that I'm not always given process 3? I'm guessing I must have rebooted without doing an "endcli", but I'm not 100% sure.

Cheers!

[Opus]

process 1 and 2 are most likely running in the background (workbench), not having closed them before will not have it open next time you boot.  if you type status into a cli it will tell you what is running, and break 2 would kill process 2.  good luck

[motorollin]

Rebooting without doing endcli won't cause this. If you really want to kill it, open up a shell and type:

status

then press return. This will show all of the running processes. Then type

break processnumber

where processnumber is the number of the process you want to break (obviously )

However, it may just be the case that something in your startup-sequence or user-startup have used the Run command to detach to their own shell, which IIRC will cause subsequent shells to have a different number (since they're numbered consecutively).

Edit - Opus beat me to it

Also, to give an example of how normal this is, my 3.1 installation inside UAE has quite a few patches loading on boot, and opening up a shell starts process 10. So I really wouldn't worry about it.

[jkirk]

it has been so long since i dealt with this i don't know if this helps but i think when you have a batch file such as startup_sequence it opens a shell while working. as long as the program started by this batch file is running that shell won't close. well unless the output is sent to >nil or >null. so chances are those shell processes are being held open by a certain process.

dangit i got bea by two people. i suck at typing.

[motorollin]

it has been so long since i dealt with this i don't know if this helps but i think when you have a batch file such as startup_sequence it opens a shell while working. as long as the program started by this batch file is running that shell won't close. well unless the output is sent to >nil or >null. so chances are those shell processes are being held open by a certain process.

Even if you use run, each programme which gets loaded is still a process so will still shift the next shell's process number along by 1. Using Run just detaches it from the current shell processes (allowing e.g. startup-sequence to continue running without waiting for the other programme to finish what it's doing). Redirecting output to NIL just means you don't see the text telling you which shell process has been created for the command.

[jkirk]

Even if you use run, each programme which gets loaded is still a process so will still shift the next shell's process number along by 1. Using Run just detaches it from the current shell processes (allowing e.g. startup-sequence to continue running without waiting for the other programme to finish what it's doing). Redirecting output to NIL just means you don't see the text telling you which shell process has been created for the command.

yea that's right. it has been so long i am a bit rusty.:lol:

[motorollin]

yea that's right. it has been so long i am a bit rusty.:lol:

I had to check myself