Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
I'm not sure why you would want to do that, but I'll show you how. . .
Before you start, you really should read the man pages on both klogd and agetty (man klogd; man agetty).
klogd is the kernel system message logger, and if it's disabled, you won't
get any messages about what your system is doing. If you have any errors (on loading modules, for example), you won't be able to get any meaningful output from the kernel.
Anway, enough with the lecturing:
grep klogd *
you'll get something like:
rc.syslog: if [ -x /usr/sbin/syslogd -a -x /usr/sbin/klogd ]; then
rc.syslog: echo -n "Starting sysklogd daemons: "
rc.syslog: sleep 1 # prevent syslogd/klogd race condition on SMP kernels
rc.syslog: echo " /usr/sbin/klogd -c 3 -x"
rc.syslog: /usr/sbin/klogd -c 3 -x
rc.syslog: killall klogd 2> /dev/null
the first field is the filename that contains klogd, so edit that file (in this
case, rc.syslog) and comment out the lines above (don't forget to comment out the "fi" that closes the if statement).
agetty is used for allowing multiple "virtual consoles" access to which is
gained by hitting Alt-F1, Alt-F2...Alt-F6 (or more). This ability can really aid
in debugging (especially if you have problems with X). You can switch from X by hitting Ctrl-Alt-F6, and fix whatever problems you're having, say
Netscape has frozen X completely, but you can't reboot because you're in
the middle of FTPing a large file from work. You can switch to console
mode, kill netscape and switch back to X (Ctrl-Alt-F7) and let your FTP
session finish. If you disable all of the gettys, you will not be able to do that.
Anyway, enough with the lectures.
To disable gettys, edit your /etc/inittab file and comment out the lines:
# These are the standard console login getties in multiuser mode:
c1:1235:respawn:/sbin/agetty 38400 tty1 linux
c2:1235:respawn:/sbin/agetty 38400 tty2 linux
c3:1235:respawn:/sbin/agetty 38400 tty3 linux
c4:1235:respawn:/sbin/agetty 38400 tty4 linux
c5:1235:respawn:/sbin/agetty 38400 tty5 linux
c6:12345:respawn:/sbin/agetty 38400 tty6 linux
Read a couple of lines down (don't comment out this, just read it):
# Runlevel 4 used to be for an X window only system, until we discovered
# that it throws init into a loop that keeps your load avg at least 1 all
# the time. Thus, there is now one getty opened on tty6. Hopefully no one
# will notice. ;^)
# It might not be bad to have one text console anyway, in case something
# happens to X.
Before you do any of this, make sure you know how to boot from a boot
disk (CDROM or floppy) and fix these files if something goes horribly wrong.
I would totally not recommend disabling these. What would be your purpose in getting rid of these, first off, they don't take up too much space or resources, so I see no real reason to stop these processes.
I'd say not a good idea either, I really enjoy these features. One of my favorite things about linux is being able to have 6 different logins doing 6 different things. And the kernel messages, oh I think I'd still be back asking how to use my mouse if I didn't have those.
Same deal. Those are all complex programs, loading external plugins et all. That's why I am saying try a simple program, something like vi. If you get vi showing 5 processes, then I'd probably dig up something on google.com/linux if I were you, and see what the deal is. But I am guessing that it's because these are complex programs, not simple command line text editors.