Hi. We have a QNX machine running as a dedicated development box. At
any given time, there are probably 10 people working on it
simultaneously. Primarily all we run on is the Watcom development
toolchain; testing of code is done on other machines. People connect
with it via Phindows, xterms, and telnet sessions.
Periodically, we get a pdm process running READY. Since pdm is priority
10, the compilers (at priority 9) can’t run. The pdm is easy to kill,
with a simple ‘kill -9’. It is annoying to have to kill these processes
once a day (on average); is there anything we can do to eliminate this
problem? The results of ‘sin ver’ follows; I can post anything else
that might be of use, also. Thanks in advance for any help.
sin ver:
sys/Proc32 Proc 4.25I Nov 25 1998
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24T Feb 26 1999
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.aha7scsi scsi 4.24M Mar 23 1998
//9/bin/Dev32 Dev32 4.23G Oct 04 1996
//9/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//9/bin/Dev32.ser Dev32.ser 4.23I Jun 27 1997
//9/bin/Dev32.par Dev32.par 4.23G Oct 04 1996
//9/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//9/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//9/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//9/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//9/bin/Pipe Pipe 4.23A Feb 26 1996
//9/bin/Net Net 4.25B Jul 27 1998
//9/bin/Net.ct100tx Net.ct100tx 4.23C May 02 1997
//9/bin/Mouse Mouse 4.24A Aug 22 1997
//9/bin/cron cron 4.23B Oct 30 1997
//9//usr/ucb/Tcpip Tcpip 5.00X Jul 30 1999
//9//photon/bin/Photon Photon 1.14B Sep 03 1999
//9/bin/cron cron 4.23B Oct 30 1997
//9//bin/phfontpfr Photon Font 1.14F Oct 27 1999
//9/bin/SMBfsys SMBfsys 1.30H Feb 09 1999
//9//photon/bin/Photon Photon 1.14B Sep 03 1999
//9//photon/bin/Photon Photon 1.14B Sep 03 1999
//9//photon/bin/Photon Photon 1.14B Sep 03 1999
//9//photon/bin/Photon Photon 1.14B Sep 03 1999
//9//photon/bin/Photon Photon 1.14B Sep 03 1999
//9/*/photon/bin/Photon Photon 1.14B Sep 03 1999
Josh Hamacher
FAAC Incorporated
“Josh Hamacher” <hamacher@faac.com> wrote in message
news:3A840940.6B9D24CA@faac.com…
Periodically, we get a pdm process running READY. Since pdm is priority
10, the compilers (at priority 9) can’t run. The pdm is easy to kill,
with a simple ‘kill -9’. It is annoying to have to kill these processes
once a day (on average); is there anything we can do to eliminate this
problem? The results of ‘sin ver’ follows; I can post anything else
that might be of use, also. Thanks in advance for any help.
We have a similar setup here but only a few users so QNX is not under any
strain like your setup. Is your QNX box running Photon all the time?? Our
development box just sits at the command/login prompt and pdm is launched
and stopped for each Phindows session so if you are not using Phindows
then no pdm…
Its not much of a fix but maybe a small work around…
Good luck…
~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ http://www.michiganscientific.com
~ mailto:<Lee.R.Copp@MichiganScientific.com>
Josh Hamacher <hamacher@faac.com> wrote:
Usually happens because there is a corrupt pdm.cfg file in the
$HOME/.photon/pdm directory. Remove that file, and you should
be ok.
-David
Hi. We have a QNX machine running as a dedicated development box. At
any given time, there are probably 10 people working on it
simultaneously. Primarily all we run on is the Watcom development
toolchain; testing of code is done on other machines. People connect
with it via Phindows, xterms, and telnet sessions.
–
QNX Training Services
dagibbs@qnx.com
Okay, I’ll just have to try to figure out which user it, and then blow
away their pdm.cfg file. Thanks for the tip.
Josh
David Gibbs wrote:
Josh Hamacher <> hamacher@faac.com> > wrote:
Usually happens because there is a corrupt pdm.cfg file in the
$HOME/.photon/pdm directory. Remove that file, and you should
be ok.
-David
Hi. We have a QNX machine running as a dedicated development box. At
any given time, there are probably 10 people working on it
simultaneously. Primarily all we run on is the Watcom development
toolchain; testing of code is done on other machines. People connect
with it via Phindows, xterms, and telnet sessions.
–
QNX Training Services
dagibbs@qnx.com
Josh Hamacher <hamacher@faac.com> wrote:
Okay, I’ll just have to try to figure out which user it, and then blow
away their pdm.cfg file. Thanks for the tip.
If you can find the pdm that is running ready, find the user name is
pretty simple, try: “sin fo nibgUL”.
-David
QNX Training Services
dagibbs@qnx.com
Pretty simple? Yeah, that looks intuitively obvious to me. Thanks
again, though, I can easily get the specific pdm with ‘ps -A | fgrep
READY’.
Josh
David Gibbs wrote:
Josh Hamacher <> hamacher@faac.com> > wrote:
Okay, I’ll just have to try to figure out which user it, and then blow
away their pdm.cfg file. Thanks for the tip.
If you can find the pdm that is running ready, find the user name is
pretty simple, try: “sin fo nibgUL”.
-David
QNX Training Services
dagibbs@qnx.com
Josh Hamacher <hamacher@faac.com> wrote:
Pretty simple? Yeah, that looks intuitively obvious to me. > > Thanks
again, though, I can easily get the specific pdm with ‘ps -A | fgrep
READY’.
Well, then, do it all in one line…
sin fo nibgUL | fgrep READY
-David
QNX Training Services
dagibbs@qnx.com
Hi. I just wanted to say thanks again - I think I found (and
eliminated) the corrupt pdm.cfg.
Josh
David Gibbs wrote:
Josh Hamacher <> hamacher@faac.com> > wrote:
Pretty simple? Yeah, that looks intuitively obvious to me. > > Thanks
again, though, I can easily get the specific pdm with ‘ps -A | fgrep
READY’.
Well, then, do it all in one line…
sin fo nibgUL | fgrep READY
-David
QNX Training Services
dagibbs@qnx.com