Hello!
When I see a process in the tasklist (by AROS tasklist command) and even it isn’t in the process list of actual Shell (by status).
With the:
break C|D|E|F name=<process_not_in_status_list>
do nothing!
Why can we allow to send this signals with break CMD even if not in status task list, but process in general tasklist?
Is it really too dangerous? But an option would be nice?
Sincerely your,
DGILLES
Break AmigaDOS CMD generalization
Re: Break AmigaDOS CMD generalization
Are you sure? So you are comparing AROS with OS4 and found OS4 allows it? Does it actually work?
I've just done some testing in two shells. Status know about the processes in each shell. Number and name.
I ran a hanging "Dir ?" in one shell and tried to break it in another shell. I gave process name then number to Break and it didn't break it. I then got out Ranger to look up process names and sent a few across. Break couldn't find the process. I then gave it the process name of the shell and window. It couldn't find any process to break. How have you been able to break past this defense?
I've just done some testing in two shells. Status know about the processes in each shell. Number and name.
I ran a hanging "Dir ?" in one shell and tried to break it in another shell. I gave process name then number to Break and it didn't break it. I then got out Ranger to look up process names and sent a few across. Break couldn't find the process. I then gave it the process name of the shell and window. It couldn't find any process to break. How have you been able to break past this defense?