/usr/sbin/getty ?

[steven Burgess_2]

I'm just investigating performance on one of our servers. Memory is getting hammered.

It's a finance system so I'm just speaking with applications regarding whats happening on the server at the moment.

There are no unusually large hoggers, apart from , if i do

w | more

i get user login id's followed by

login@ idle JCPU PCPU what
8:58am1702:39 /usr/sbin/getty console console

Can anyone explain the processes

also when I do a who-u

i get for eg

Mar 21 09:11 old 489

what does the old signify?

Any help in this matter is appreciated

Steve

[steven Burgess_2]

This box is a version 11 server. I have checked other 11 servers, the getty process (spawned by init, when users log on) appear to hang around. On version 10 systems there are no getty processes from w | more hanging around

[S.K. Chan]

The "getty" process is always there (regardless of whether it's 11.x or 10.x), if it is spawned by inittab and user is logged in to the system directly from VUE or CDE.

The "old" from who means ( I think ), is when you got a user who logs into a system but doesn't not gracefully logs out from it, for example he/she simply close the shell/window without doing CTRL-D or logout command.

[Peter Kloetgen]

Hi Steven,

getty- processes manage the login of users. They take the information given by users when logging onto the system, password and username. These processes look into the systems configuration files and confirm the given information. (/etc/passwd, /etc/group, shadow files) Only if the information is ok, the user can logon to the system. They also initialise the terminals for users.

Allways stay on the bright side of life!

Peter

[MANOJ SRIVASTAVA]

HI Steven

Getty is a process that sends login prompt to the serial port and then helps in logging in. The getty for the console to get login . Please donot do anyhtin to this as your consloe login will disappear. The same is enabled through the /etc/inittab file.

However your memory problm should not be realted to this at all . If possible do a top -h , vmstat or sar to know the initial area of problem . There can be runaway process which may be holding on . If you have glance than it may be more easier.


Manoj Srivastava

[BFA6]

Hi,

Try running glance if you have it.

Regards,

Hilary