processes running for long

[Sugata]

Hi,
Some processes are running for very log in a HP-11.2.0 machine. If I kill those processes some others are taking the place. I am attching the log.
I got help previously from you all, so looking forward.

Regards,
Sugata

[steven Burgess_2]

Hi Sugata

The processes you have running are more than valid. Looks like someone has a dtterm session (which is your dtterm)

man dtterm for more info

Your xset is a user preference utility for x

man xset

dtprintinfo is the CDE print viewer

man dtprintinfo

The perl process could when be a job or programme your user vijayvk has running

netscape looks like a web browser someone has running

Why do you feel you need to kill these processes ?

HTH

Steve

[Paula J Frazer-Campbell]

Hi
Speak to the users of the process and find out what they are doing.

Paula

[Sugata]

The memory used is becoming 100% most of the time.
So users are not able to invoke any other process while load is ok.
Although number of users & number of processes are almost same in other servers, they don't have any problem.

[Florian Heigl (new acc)]

These processes don't have a corresponding terminal anymore. Are Your users using some kind of windoze X-Server?

In our environment this tends to happen when they simply close the Xserver application, or simply use the 'x' button instead of file->exit. I'm cleaning up those processes every now and then, but I can't really image these to be consuming enough memory to prevent people from logging on.

[steven Burgess_2]

Hi

Have a look at who is using the most memory on your system

UNIX95= ps -e -o
ruser,vsz,pid,args|sed '1d'|sort -rnk2 | more

HTH

Steve

[Bill Hassell]

xset and dtprintinfo have been orphaned by someone. Typically this is caused by PCs that crash or users that simply disconnect their sessions without stopping their programs. Neither xset nor dtprintinfo will run more than a second. Kill those processes with kill -15

As far as memory issues, swapinfo -tm will show you if memory is a problem. The Total line percentage is the most useful. If it is less than 60-80% then the memory issues are related to 32bit programs and probably shared memory. You'll need a copy of shminfo to look at shared memory, and you'll also need to look at maxdsiz in the kernel (raise it to 900 megs).