Hello,
somestimes it happens in our QNX 2.21 that a process becomes dead: prio
changes to ‘0’, status to ‘D’.
if this is running in a shell script this is blocked. There seems to be no
possiblity to kill/slay the dead process. We can continue only by killing
the father shell.
To now we’ve no chance to remove this processes but booting the node.
Is there any solution for this problem?
THX
Georg Pohl
PS: in most cases they are programs/commands like cp, cat or backup which
will become dead.
Georg Pohl
Previously, Georg Pohl wrote in qdn.public.qnx2:
somestimes it happens in our QNX 2.21 that a process becomes dead: prio
changes to ‘0’, status to ‘D’.
if this is running in a shell script this is blocked. There seems to be no
possiblity to kill/slay the dead process. We can continue only by killing
the father shell.To now we’ve no chance to remove this processes but booting the node.
Is there any solution for this problem?
This is a very old problem. The only instance I recall like
this goes as follows. You have an administrator that
receives obituaries. This program becomes hung in some way.
It gets sent an obituary, but does not relay it. The
program trying to die now can’t, so it shows up as DEAD.
The way to solve this is to kill the administrator.
Eventually an entire system can be locked up this way.
Mitchell Schoenbrun --------- maschoen@pobox.com
Mitchell Schoenbrun wrote …
This is a very old problem. The only instance I recall like
this goes as follows. You have an administrator that
receives obituaries. This program becomes hung in some way.
It gets sent an obituary, but does not relay it. The
program trying to die now can’t, so it shows up as DEAD.
The way to solve this is to kill the administrator.
Eventually an entire system can be locked up this way.
THX, Mitchell
seems as if there is no way to get these processes freed 
Regards
Georg Pohl
what i would look for are any programs that have the informed flag set.
tsk flags i believe is the right one to use. look for the i flag
some normal informed admins are ‘dumper’. but this source was opened so many
people wrote their own versions. if they do not relay the death message
correctly then processes will not be allowed to die.
Georg Pohl <pohl.wvz@klosterfrau.de> wrote:
Mitchell Schoenbrun wrote …
This is a very old problem. The only instance I recall like
this goes as follows. You have an administrator that
receives obituaries. This program becomes hung in some way.
It gets sent an obituary, but does not relay it. The
program trying to die now can’t, so it shows up as DEAD.
The way to solve this is to kill the administrator.
Eventually an entire system can be locked up this way.
THX, Mitchellseems as if there is no way to get these processes freed >
Regards
Georg Pohl
–
Randy Martin randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
Randy Martin schrieb in Nachricht <9i2i4q$8ao$1@nntp.qnx.com>…
what i would look for are any programs that have the informed flag set.
tsk flags i believe is the right one to use. look for the i flag
some normal informed admins are ‘dumper’. but this source was opened so
many
people wrote their own versions. if they do not relay the death message
correctly then processes will not be allowed to die.
Sorry, but my system does not have these infos.
“tsk flags” is unknown in my QNX 2.21 which offers some flag-infos:
F uses floating pount (8087 hehe)
H loaded in high memory
L locked in memory
O change owner
P privikeged
R remote cretaes ok
S shareable
there is “tsk” with no arguments:
A administrator
C concurrent execution
D doomed (I called it dead)
E Escaped shell
H to be held
L locked in memory
N new task entry in the process
of beeing created
There’s no informed flag
The processes which become doomed (or dead) are standard cmds beeing part of
the QNX installation. Their fathers are simple shells (not administrator
tasks)
Are you speakin about another release of QNX?
THX
Georg
look at output of ‘tsk’ command. in the flags column you will see a bunch
of letters. look for the I… should be bit 9 from the right.
Georg Pohl <pohl.wvz@klosterfrau.de> wrote:
Randy Martin schrieb in Nachricht <9i2i4q$8ao$> 1@nntp.qnx.com> >…
what i would look for are any programs that have the informed flag set.tsk flags i believe is the right one to use. look for the i flag
some normal informed admins are ‘dumper’. but this source was opened so
many
people wrote their own versions. if they do not relay the death message
correctly then processes will not be allowed to die.
Sorry, but my system does not have these infos.“tsk flags” is unknown in my QNX 2.21 which offers some flag-infos:
F uses floating pount (8087 hehe)
H loaded in high memory
L locked in memory
O change owner
P privikeged
R remote cretaes ok
S shareablethere is “tsk” with no arguments:
A administrator
C concurrent execution
D doomed (I called it dead)
E Escaped shell
H to be held
L locked in memory
N new task entry in the process
of beeing createdThere’s no informed flag >
The processes which become doomed (or dead) are standard cmds beeing part of
the QNX installation. Their fathers are simple shells (not administrator
tasks)Are you speakin about another release of QNX?
THX
Georg
–
Randy Martin randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
Georg Pohl <pohl.wvz@klosterfrau.de> wrote:
Randy Martin schrieb in Nachricht <9i2i4q$8ao$> 1@nntp.qnx.com> >…
what i would look for are any programs that have the informed flag set.tsk flags i believe is the right one to use. look for the i flag
some normal informed admins are ‘dumper’. but this source was opened so
many
people wrote their own versions. if they do not relay the death message
correctly then processes will not be allowed to die.
Sorry, but my system does not have these infos.
The processes which become doomed (or dead) are standard cmds beeing part of
the QNX installation. Their fathers are simple shells (not administrator
tasks)
He is not suggesting that the zombie tasks are special themselves – but
that there is some other task that has this flag set, and isn’t doing
things properly that is causing these tasks to end up in the dead but
not cleaned up state. The particular flag does exist under QNX2, and
it gave whichever tasks set it a system-wide effect – not just on their
children.
Are you speakin about another release of QNX?
No, he isn’t.
(If he talking about QNX4, he’d talk about the sin utility, and for
QNX6, it would be pidin.)
QNX Training Services
dagibbs@qnx.com
Previously, Randy Martin wrote in qdn.public.qnx2:
look at output of ‘tsk’ command. in the flags column you will see a bunch
of letters. look for the I… should be bit 9 from the right.
If you look at the first three lines from running “tsk” you will
see that task, fsys, and dev all have the flags - - - I P L A - - - - -
turned on. Take a look at your other programs for the ‘I’ flag.
Mitchell Schoenbrun --------- maschoen@pobox.com
David Gibbs wrote…
Georg Pohl <> pohl.wvz@klosterfrau.de> > wrote:
He is not suggesting that the zombie tasks are special themselves – but
that there is some other task that has this flag set, and isn’t doing
things properly that is causing these tasks to end up in the dead but
not cleaned up state. The particular flag does exist under QNX2, and
it gave whichever tasks set it a system-wide effect – not just on their
children.
OK - I got it. Case of temporary blindness
I’ve to wait until it occurs again that a job becomes dead/doomed.
THX for your patience and answers
Georg