A program forks itself into 8 copies.
Sin shows the same executable.
Is it possible for “sin” to show a more appropriate
(for the application) name in this display?
–
Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/
Alex/Systems 104 wrote:
A program forks itself into 8 copies.
Sin shows the same executable.
Is it possible for “sin” to show a more appropriate
(for the application) name in this display?
sin shows the name of the process. Seems pretty reasonable to show the
unique pid and process name - there is no ambiguity. Systems bank on
this behaviour, changing it now would cause much pain to people with
little benefit.
\
Cheers,
Adam
QNX Software Systems
[ amallory@qnx.com ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
On Wed, 27 Jul 2005 15:50:27 +0200, Adam Mallory <amallory@qnx.com> wrote:
sin shows the name of the process. Seems pretty reasonable to show the
unique pid and process name - there is no ambiguity. Systems bank on
this behaviour, changing it now would cause much pain to people with
little benefit.
Sure
Just want to save a step having to look up the pseudo “process name”
via sin name and then to interpret sin…
So no manipulation possibility e.g. via the environment variables
or something obscure?
Reason for this:
Multi process, multi-executable application was converted to a
single executable, multi process (due to ease of installation
and configuration). Previously sin would show the unique
process name, now of course it all shows the same process name.
–
Using Opera’s revolutionary e-mail client: http://www.opera.com/m2/
Alex/Systems 104 wrote:
Sure
Just want to save a step having to look up the pseudo “process name”
via sin name and then to interpret sin…
Why go a custom sin route (seems rather heavy handed IMHO)?
Instead have each of your ‘sub processes’ respond to version messages
and then sin ver will let you differentiate them all (by name and/or ver
num). Additionally you could uses scripts with sed/awk to get more
complicated.
This way, no custom version of tools is required (saves you headaches in
the long run anyways).
So no manipulation possibility e.g. via the environment variables
or something obscure?
If you wish the sin -alex_systems_104_process_name_mangler option, you
should speak to your sales rep about custom engineering.
–
Cheers,
Adam
QNX Software Systems
[ amallory@qnx.com ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
On Wed, 27 Jul 2005 21:00:04 +0200, Adam Mallory <amallory@qnx.com> wrote:
Instead have each of your ‘sub processes’ respond to version messages
and then sin ver will let you differentiate them all (by name and/or ver
num). Additionally you could uses scripts with sed/awk to get more
complicated.
Good idea.
However sin gives the full picture, sin ver only those processes that
respond to version.
This way, no custom version of tools is required (saves you headaches in
the long run anyways).So no manipulation possibility e.g. via the environment variables
or something obscure?If you wish the sin -alex_systems_104_process_name_mangler option, you
should speak to your sales rep about custom engineering.
No, it was not the intention at all to have a custom sin.
Just to present to sin (or Proc) when it wants the
process name to be able to return a different name than
the name stored on disk…
If it’s not possible, then sin ver it will have to be.
On Thu, 28 Jul 2005 12:02:41 +0200, Alex/Systems 104
<acellarius@yah0o.lsd.com> wrote:
On Wed, 27 Jul 2005 21:00:04 +0200, Adam Mallory <> amallory@qnx.com
wrote:Instead have each of your ‘sub processes’ respond to version messages
and then sin ver will let you differentiate them all (by name and/or
ver num). Additionally you could uses scripts with sed/awk to get more
BTW
It seems sin ver only accepts the first version from
these forked processes, as only 1 version is displayed, even
though the version request is received and responded to in
the same way…
Alex/Systems 104 wrote:
On Thu, 28 Jul 2005 12:02:41 +0200, Alex/Systems 104
acellarius@yah0o.lsd.com> > wrote:On Wed, 27 Jul 2005 21:00:04 +0200, Adam Mallory <> amallory@qnx.com
wrote:Instead have each of your ‘sub processes’ respond to version
messages and then sin ver will let you differentiate them all (by
name and/or ver num). Additionally you could uses scripts with
sed/awk to get more
BTW
It seems sin ver only accepts the first version from
these forked processes, as only 1 version is displayed, even
though the version request is received and responded to in
the same way…
Bummer - then I guess a script will be what you need to write tie the
two bits of info you wish together.
–
Cheers,
Adam
QNX Software Systems
[ amallory@qnx.com ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
Look at sin ve and the VERSION MESSAGE for a program. You can return any
text you want to program name etc. sin ve is very useful. I wish it were
available in QNX 6. I have also used it to display status information about
a program. Just remember that you MUST respond to sin ve message very
quickly or the system will come crashing to it’s knees…
“Alex/Systems 104” <acellarius@yah0o.lsd.com> wrote in message
news:op.suj9qsgwbinb6v@alex-pentium-m…
A program forks itself into 8 copies.
Sin shows the same executable.
Is it possible for “sin” to show a more appropriate
(for the application) name in this display?–
Using Opera’s revolutionary e-mail client: > http://www.opera.com/m2/
Do your forking first, then prepare to respond to the version message.
“Adam Mallory” <amallory@qnx.com> wrote in message
news:dcbg96$ljg$1@inn.qnx.com…
Alex/Systems 104 wrote:
On Thu, 28 Jul 2005 12:02:41 +0200, Alex/Systems 104
acellarius@yah0o.lsd.com> > wrote:On Wed, 27 Jul 2005 21:00:04 +0200, Adam Mallory <> amallory@qnx.com
wrote:Instead have each of your ‘sub processes’ respond to version
messages and then sin ver will let you differentiate them all (by
name and/or ver num). Additionally you could uses scripts with
sed/awk to get more
BTW
It seems sin ver only accepts the first version from
these forked processes, as only 1 version is displayed, even
though the version request is received and responded to in
the same way…Bummer - then I guess a script will be what you need to write tie the
two bits of info you wish together.–
Cheers,
AdamQNX Software Systems
[ > amallory@qnx.com > ]With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
Adam Mallory wrote:
Bummer - then I guess a script will be what you need to write tie the
two bits of info you wish together.
Hold on a sec - I just tried an example to respond to versions with
different names (after fork()) and it works fine (different names,
versions, letters etc).
You must be doing something wrong in app.
–
Cheers,
Adam
QNX Software Systems
[ amallory@qnx.com ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
Bill Caroselli <qtps@earthlink.net> wrote:
Look at sin ve and the VERSION MESSAGE for a program. You can return any
text you want to program name etc. sin ve is very useful. I wish it were
available in QNX 6. I have also used it to display status information about
a program. Just remember that you MUST respond to sin ve message very
quickly or the system will come crashing to it’s knees…
Actually, you don’t have to reply to “sin ve” very quickly – the only
thing not replying will do is cause “sin ve” to hang for an extended
period of time. (Getting version request messages requires setting
PPF_SERVER, to request them.)
It is not replying to death messages in a timely fashion (should you
set PPF_INFORM) that will do bat things ™ to the system.
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
On Tue, 02 Aug 2005 21:26:00 +0200, Adam Mallory <amallory@qnx.com> wrote:
Adam Mallory wrote:
Bummer - then I guess a script will be what you need to write tie the
two bits of info you wish together.Hold on a sec - I just tried an example to respond to versions with
different names (after fork()) and it works fine (different names,
versions, letters etc).You must be doing something wrong in app.
That’s odd.
I can see each process is getting the system message.
Each one responds with different info, but only
the first forked process’ information get displayed.
The other’s information is not displayed.
On Tue, 02 Aug 2005 20:03:11 +0200, Bill Caroselli <qtps@earthlink.net>
wrote:
Look at sin ve and the VERSION MESSAGE for a program. You can return any
text you want to program name etc. sin ve is very useful. I wish it were
available in QNX 6. I have also used it to display status information
about
a program. Just remember that you MUST respond to sin ve message very
quickly or the system will come crashing to it’s knees…
Thanks Bill, I’ve implemented this
Alex/Systems 104 wrote:
That’s odd.
I can see each process is getting the system message.
Each one responds with different info, but only
the first forked process’ information get displayed.
The other’s information is not displayed.
Then you are not replying with what you think you are. I’ve attached an
example.
–
Cheers,
Adam
QNX Software Systems
[ amallory@qnx.com ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
I guess your right. It’s been about 4 years since I’ve worked on QNX4.
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:dcolee$a8t$1@inn.qnx.com…
Bill Caroselli <> qtps@earthlink.net> > wrote:
Look at sin ve and the VERSION MESSAGE for a program. You can return
any
text you want to program name etc. sin ve is very useful. I wish it
were
available in QNX 6. I have also used it to display status information
about
a program. Just remember that you MUST respond to sin ve message very
quickly or the system will come crashing to it’s knees…Actually, you don’t have to reply to “sin ve” very quickly – the only
thing not replying will do is cause “sin ve” to hang for an extended
period of time. (Getting version request messages requires setting
PPF_SERVER, to request them.)It is not replying to death messages in a timely fashion (should you
set PPF_INFORM) that will do bat things ™ to the system.-David
David Gibbs
QNX Training Services
dagibbs@qnx.com