sin Defaults

When I use the command sin with no arguments, what is the default output in
each of the columns? It appears the last column is some sort of time, but
the Momentics documentation describes it as milliseconds. If that is the
case, the following reply makes no sense

sin -P io-net

io-net 8198 56K 472K 164K 1121K 5062407

Is is possible in a later rev to get column headers?

Thanks,
David Kuechenmeister

Never mind about the first part, I realized it was the number of
milliseconds since the program started.

But it would be nice to see column headers.

“David Kuechenmeister” <david.kuechenmeister@viasat.com> wrote in message
news:bcmtp6$h5f$1@inn.qnx.com

When I use the command sin with no arguments, what is the default output
in
each of the columns? It appears the last column is some sort of time, but
the Momentics documentation describes it as milliseconds. If that is the
case, the following reply makes no sense

sin -P io-net

io-net 8198 56K 472K 164K 1121K
5062407

Is is possible in a later rev to get column headers?

Thanks,
David Kuechenmeister

David Kuechenmeister wrote:

sin -P io-net

io-net 8198 56K 472K 164K 1121K
5062407

Is is possible in a later rev to get column headers?

I’m not sure (I don’t speak for QSSL) but I think that sin is destined for
/dev/null, and that pidin is the replacement (why pidin doesn’t have a
filter by name - rather than pid - feature; I don’t know).

I’m not sure (I don’t speak for QSSL) but I think that sin is destined for
/dev/null, and that pidin is the replacement (why pidin doesn’t have a
filter by name - rather than pid - feature; I don’t know).

Sin was basically just a test driver for psin. It got shipped but never
finished. Pidin is the one to use on Neutrino.

And by the way:

ren:/home/kewarken >pidin -p io-net
pid tid name prio STATE Blocked
77842 1 sbin/io-net 10o SIGWAITINFO
77842 2 sbin/io-net 10o RECEIVE 1
77842 3 sbin/io-net 10o RECEIVE 1
77842 4 sbin/io-net 10o RECEIVE 1
77842 5 sbin/io-net 10o RECEIVE 6
77842 6 sbin/io-net 10o RECEIVE 1
77842 7 sbin/io-net 21r RECEIVE 22
77842 8 sbin/io-net 21o RECEIVE 33
77842 10 sbin/io-net 21r CONDVAR 80d90ac

cheers,

Kris

Yes, but it’s only an exact match filter, whereas sin takes a partial match…

Kris Warkentin <kewarken@qnx.com> wrote:

I’m not sure (I don’t speak for QSSL) but I think that sin is destined for
/dev/null, and that pidin is the replacement (why pidin doesn’t have a
filter by name - rather than pid - feature; I don’t know).

Sin was basically just a test driver for psin. It got shipped but never
finished. Pidin is the one to use on Neutrino.

And by the way:

ren:/home/kewarken >pidin -p io-net
pid tid name prio STATE Blocked
77842 1 sbin/io-net 10o SIGWAITINFO
77842 2 sbin/io-net 10o RECEIVE 1
77842 3 sbin/io-net 10o RECEIVE 1
77842 4 sbin/io-net 10o RECEIVE 1
77842 5 sbin/io-net 10o RECEIVE 6
77842 6 sbin/io-net 10o RECEIVE 1
77842 7 sbin/io-net 21r RECEIVE 22
77842 8 sbin/io-net 21o RECEIVE 33
77842 10 sbin/io-net 21r CONDVAR 80d90ac

cheers,

Kris


cburgess@qnx.com

Colin Burgess wrote:

Yes, but it’s only an exact match filter, whereas sin takes a partial
match…

Yes, and this is often useful. For instance, our software all resides one
path, and the name of the product is part of the path, so (on QNX4) we can:

sin -P{productname}

to get a list of just our software. I use this all the time. I did not
know, however, that the process name could be specified instead of simply
the pid to pidin, so thanks to Kris for that.

Now; not to seem ungrateful for the pointer, but perhaps a change to the
usemsg would be appropriate ?

Rennie <rallen@csical.com> wrote:
: Now; not to seem ungrateful for the pointer, but perhaps a change to the
: usemsg would be appropriate ?

I’m pleased to see that the docs mention it:

-P pid Show only the process family you’re interested in (pid may be
a name or number).

-p pid Show only the process you’re interested in (pid may be a
name or number).


Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

I did not
know, however, that the process name could be specified instead of simply
the pid to pidin, so thanks to Kris for that.

…perhaps a change to the usemsg would be appropriate ?

PR’d.

\

Doug Smith
Technical Publications
QNX Software Systems