questions about "htop" details

SaintDanBert · 09-21-2010, 03:49 PM

When I run htop on my laptop, I see several things that I don't understand.

Can someone please explain why I might see these things?

Can someone tell me how to change what is going on?

I understood the system-V-init approach. I'm still working to wrap around the "upstart" approach to system startup.

I see copies of rtkit-daemon. This feels like a bad thing. How do I get rid of this ... if it really is a bad thing?

I see several copies of the syslogd process running. Are these always there or are several launched based upon logging needs? If I'm doing that much logging, how do I sort out what is going on?

I have a screen full of console-kit-daemon entries. I really don't understand why I need them.

I really don't want more than two copies of getty. where do I configure to reduce the number?

Merci d'avance,
~~~ 0;-Dan

AlucardZero · 09-21-2010, 04:49 PM

Quote:

rtkit-daemon. This feels like a bad thing.

Why... ? `dpkg -S /usr/lib/rtkit/rtkit-daemon` -> `apt-cache show rtkit` ->

Quote:

RealtimeKit is a D-Bus system service that changes the scheduling policy of user processes/threads to SCHED_RR (i.e. realtime scheduling mode) on request. It is intended to be used as a secure mechanism to allow real-time scheduling to be used by normal user processes.

IOW, leave it.

Quote:

I have a screen full of console-kit-daemon entries.

Same method of research ->

Quote:

ConsoleKit is a system daemon for tracking what users are logged into the system and how they interact with the computer (e.g. which keyboard and mouse they use).

It provides asynchronous notification via the system message bus.

Sounds like that many threads is normal. In htop, if you hit F2, then enable Display Options -> Hide Userland Threads, it should only show one line of console-kit-daemon.

Quote:

I really don't want more than two copies of getty.

Comment out some getty lines from /etc/inittab and run `init q`

Disclaimer: You didn't specify what distro you're running. I assumed Ubuntu like your profile says.
Disclaimer 2: I have never used upstart so my getty advice might be wrong.

SaintDanBert · 09-23-2010, 03:39 AM

Quote:

Originally Posted by AlucardZero

...
Comment out some getty lines from /etc/inittab and run `init q`
...
Disclaimer 2: I have never used upstart so my getty advice might be wrong.

No harm, but "upstart" doesn't use /etc/inittab but I'd forgotten that details. When I find where U/S puts its getty requirements, I'll post my results.

Merci d'avance,
~~~ 0;-Dan

SaintDanBert · 09-23-2010, 03:53 AM

Under Ubuntu Jaunty, I find:

Code:

/etc/event.d
    tty1  tty2  tty3  tty4  tty5  tty6

Each of these files contains: ("tty1" as an example)

Code:

# tty1 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.

start on stopped rc2
start on stopped rc3
start on stopped rc4
start on stopped rc5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /sbin/getty 38400 tty1

Refer to the Upstart Documentation http://upstart.ubuntu.com/wiki/ to understand these "jobs".

NOTE -- Ubuntu has used upstart for a while. Their web site names v6.10. The current release is v10.04-LTS with
another release scheduled in October 2010. Each release has deployed more and more use of upstart as both upstart and ubuntu matured. Because the system-V init was around for sooooooo loooooong, upstart made some effort to "look like" the olde stuff.

I will suss out how this looks for Lucid (v10.04 LTS) and post that separately.

Cheers,
~~~ 0;-Dan

SaintDanBert · 09-23-2010, 11:03 AM

Under Ubuntu Lucid, I find:

Code:

/etc/init
    tty1.conf  tty2.conf  tty3.conf  tty4.conf  tty5.conf  tty6.conf

Each of these files contains: ("tty1" as an example)

Code:

# tty1 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.

start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]

respawn
exec /sbin/getty -8 38400 tty1

NOTICE -- This is a much simpler "job" file than appeared in Jaunty. This results because of improvement in job-file features implemented by the newer "upstart." Also, we getty still runs at the same baud rate and name, but we indicate an 8-bit clean "-8" connection.

(Refer to the Upstart Documentation http://upstart.ubuntu.com/wiki/ to understand these "jobs".)

Cheers,
~~~ 0;-Dan[/QUOTE]