How do I kill kde and return the server to just a login so that I can save on resources. I have never done this as I am a child of the gui and it is killing my web server on the net. Paul
On Thursday 23 October 2003 4:24 pm, Paul Taylor wrote:
How do I kill kde and return the server to just a login so that I can save on resources. I have never done this as I am a child of the gui and it is killing my web server on the net.
As root: # init 3 -- SuSE Linux 8.2 (i586) Linux 2.4.20-4GB-athlon
On Thursday 23 Oct 2003 4:30 pm, Jonathan Lim wrote:
On Thursday 23 October 2003 4:24 pm, Paul Taylor wrote:
How do I kill kde and return the server to just a login so that I can save on resources. I have never done this as I am a child of the gui and it is killing my web server on the net.
As root: # init 3
If you want this as the default at bootup, you need to change /etc/inittab so that the line id:5:initdefault: looks like id:3:initdefault: Gary -- Gary Stainburn This email does not contain private or confidential material as it may be snooped on by interested government parties for unknown and undisclosed purposes - Regulation of Investigatory Powers Act, 2000
--- Jonathan Lim
How do I kill kde and return the server to just a login so that I can save on resources. I have never done this as I am a child of the gui and it is killing my web server on the net.
As root: # init 3
That's almost correct, Jonathan :) What you would actually type is: `` telinit 3 '' However, as Gary notes, to make it permenant, you need to change your default inittab line from 5 -> 3 (for SuSE). Debian uses a different way, but that's another distro another mailing-list. HTH, -- Thomas Adam ===== Thomas Adam "The Linux Weekend Mechanic" -- www.linuxgazette.com ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk
On Thursday 23 October 2003 16:24, Paul Taylor wrote:
How do I kill kde and return the server to just a login so that I can save on resources. I have never done this as I am a child of the gui and it is killing my web server on the net. You can remain a child of the gui and use Yast :) System->Runlevel Editor->Default runlevel (which you can only see in 'expert' mode on SuSE 9.0).
Cheers -- Phil Driscoll
On Thursday 23 October 2003 4:42 pm, Thomas Adam wrote:
That's almost correct, Jonathan :) What you would actually type is:
`` telinit 3 ''
lrwxrwxrwx 1 root root 4 Jul 19 14:24 /sbin/telinit -> init Paul, you find it easier for you to do this via YAST. Yast->System->Runlevel editor Set the default to be runlevel 3. Also you may consider shutting down everything that isn't relevant to your webserver install. -- SuSE Linux 8.2 (i586) Linux 2.4.20-4GB-athlon
That's almost correct, Jonathan :) What you would actually type is:
`` telinit 3 ''
That's *quite* close, Thomas :) You may type either perhaps. init 3 has always worked for me. -- Matt ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk
Gary Stainburn wrote:
On Thursday 23 Oct 2003 4:30 pm, Jonathan Lim wrote:
On Thursday 23 October 2003 4:24 pm, Paul Taylor wrote:
How do I kill kde and return the server to just a login so that I can save on resources. I have never done this as I am a child of the gui and it is killing my web server on the net.
As root: # init 3
If you want this as the default at bootup, you need to change /etc/inittab so that the line
id:5:initdefault:
looks like
id:3:initdefault:
Gary
.. or if you prefer, add "3" to the "append" string in lilo.conf or type it in at the boot prompt e.g. "linux 3" assuming "linux" is your default image. You could even go as far as two lilo entries "kde" and "console" with the difference being the run level, then select at boot time. -- jez Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . mailto:jez@jezndi.org http://www.jezndi.org
By the way, I've noticed that if you press F2 while the machine is booting
(V9.0) it will offer the opertunity to log in at the prompt. This waits for
several seconds before continuing to the graphical login screen. I would
assume that this delay can be changed somewhere.
Adrian
----- Original Message -----
From: "Matt Johnson"
That's almost correct, Jonathan :) What you would actually type is:
`` telinit 3 ''
That's *quite* close, Thomas :) You may type either perhaps. init 3 has always worked for me.
-- Matt
________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com
--- "adrian.wells"
By the way, I've noticed that if you press F2 while the machine is booting (V9.0) it will offer the opertunity to log in at the prompt. This waits for several seconds before continuing to the graphical login screen. I would assume that this delay can be changed somewhere.
This "delay" is either the result of the slowness for the {x,g,w,k}dm init script to load, or as you say there is a delay. This delay will be defined in one of the top-level init scripts, most likely: /etc/rc.d/boot -- Thomas Adam ===== "The Linux Weekend Mechanic" -- http://linuxgazette.net "TAG Editor" -- http://linuxgazette.net "<shrug> We'll just save up your sins, Thomas, and punish you for all of them at once when you get better. The experience will probably kill you. :)" -- Benjamin A. Okopnik (Linux Gazette Technical Editor) ____________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html
Thanks, It doesn't bother me, I just thought that in some cases one may wish to increase the delay, or possible decrease it to 'improve' boot-up speed. I would assume that it's a delay, since it appears to be similar on both a P1 233 and a Athlon 2.4G - not that I've paid too much notice.
By the way, I've noticed that if you press F2 while the machine is booting (V9.0) it will offer the opportunity to log in at the prompt. This waits for several seconds before continuing to the graphical login screen. I would assume that this delay can be changed somewhere.
This "delay" is either the result of the slowness for the {x,g,w,k}dm init script to load, or as you say there is a delay. This delay will be defined in one of the top-level init scripts, most likely: /etc/rc.d/boot
participants (8)
-
adrian.wells -
Gary Stainburn -
Jez Rogers -
Jonathan Lim -
Matt Johnson -
Paul Taylor -
Phil Driscoll -
Thomas Adam