Prevent tasks listing in `ps x`

I notice that `ps x` lists tasks in Slackware 10.0, when it didn't used to in 9.0/9.1. Is there a way to prevent tasks from being listed so a daemon with several threads only shows up once?
LVL 17
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ps -aux
rstaveleyAuthor Commented:
Nope. Still lists the threads.

The 'a' and 'u' just get...

-a  all w/ tty, including other users  
-u by effective user ID (supports names)
what version do you have?
procps version 3.2.4 is the one i have

I think you will want to install the newer one.  If you have slack 10.0 then you have Version 3.2.1.
Check out the change log.

I can't reduplicate your problem.  Could I have some an example of each?
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

rstaveleyAuthor Commented:
Yes, it is 3.2.1.

I am running some proprietary software, which runs as 33 threads

On slack 10.0 (procps 3.2.1):
root@trial:~# ps x | egrep '[m]yprog'
26103 ?        Ss     0:00 /usr/local/mystuff/bin/myprog
26107 ?        S      0:00 /usr/local/mystuff/bin/myprog
26108 ?        S      0:00 /usr/local/mystuff/bin/myprog
... etc () ...
26138 ?        S      0:00 /usr/local/mystuff/bin/myprog
root@trial:~# ps x | egrep '[c]ommtouch' | wc
     33     264    5973

On slack 9.1 (procps 2.0.16)
root@qa:~# ps x | egrep '[m]yprog'
25949 ?        S      0:00 /usr/local/mystuff/bin/myprog
root@qa:~# ps x | egrep '[c]ommtouch' | wc
      1       8     181

The only thing I can see, which might provide a clue is the one entry which is 'Ss' in the 10.0 listing, which presumably is equivalent to the one and only entry in the 9.1 listing (though that one and only entry shows up as S).
rstaveleyAuthor Commented:
At, I see that version Version 3.1.14 introduced

   ps: distinct per-thread and whole-process pending signals

It isn't clear if that's something that can be switch off.

Is there a more elegant way of reproducing the old behaviour than the following?

root@trial:~# ps x | egrep 'Ss.*[m]yprog'
26103 ?        Ss     0:00 /usr/local/mystuff/bin/myprog

Have you tryed ps -e
rstaveleyAuthor Commented:
If you type `ps -e`, you get all the threads too.

root@trial:~# ps -e | egrep '[m]yprog' | wc
     33     132    1320
I am still trying to see if it is a flag somewhere.
ps is not programmed well enough for me to play with it.  

I hope this will do.
Put this either as an alias or put it into a new file called psx or something.

ps -xa --sort command,pid -o pid,stat,command | awk '{
while (i<=NF){
  isrow=isrow$i" "
if (row != isrow){
  print $0
  row = isrow
}' | sort

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rstaveleyAuthor Commented:
Nice one sigel1.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.