What's starting syslogd?


Forum: DSL Tips and Tricks
Topic: What's starting syslogd?
started by: Wittfella

Posted by Wittfella on Feb. 23 2007,03:14
Can someone tell me where in the startup sequence 'syslogd' is being started.  I have been through everwhere I can think of like inittab, RC5, RCS, knoppix_autoconfig files, but I can't find what is calling syslogd daemon.  I do not have the syslogd boot command option.

Also, as far as I can tell, if you default to runlevel 5 (ie. X gui) the actual call to 'startx' comes from ~/.bash_profile.  However its not backgrounded, so you can't use the F1 console.  If you change the line in .bash_profile to 'startx &' you can then CTRL-ALT-F1 to a usable console at the same time.  Should this be the default? Its sometimes useful to drop to a console quickly to do something.

Posted by lucky13 on Feb. 23 2007,05:20
Quote (Wittfella @ Feb. 22 2007,22:14)
Can someone tell me where in the startup sequence 'syslogd' is being started.  I have been through everwhere I can think of like inittab, RC5, RCS, knoppix_autoconfig files, but I can't find what is calling syslogd daemon.  I do not have the syslogd boot command option.

Also, as far as I can tell, if you default to runlevel 5 (ie. X gui) the actual call to 'startx' comes from ~/.bash_profile.  However its not backgrounded, so you can't use the F1 console.  If you change the line in .bash_profile to 'startx &' you can then CTRL-ALT-F1 to a usable console at the same time.  Should this be the default? Its sometimes useful to drop to a console quickly to do something.

The daemon is started at boot by init. I don't understand what you're trying to do with syslogd since it only logs system events to /var/log (unless you need to tweak it to log virtual machine/services output). It's a default daemon and doesn't require a boot code.

As far as run levels, most users are more comfortable in X than in console most of the time. Defaults are set for the comfort zone of most users, not for those who already know how to get (back) into console.

Posted by ^thehatsrule^ on Feb. 23 2007,06:28
Quote
It's a default daemon and doesn't require a boot code.
For DSL, it is disabled and requires a bootcode to save on memory/speed I would assume (and since general livecd desktop usage sessions don't really need logs)

However, I would also like to have the ctrl+alt+f1 capability by default, if there isn't any other technical problem about it.  Shouldn't be a problem for those who don't use it, as they wouldn't know the key combo and therefore would not be affected.

Posted by Wittfella on Feb. 23 2007,07:17
Quote
it is disabled and requires a bootcode to save on memory/speed

This is why I am fooling with it, just trying to squeeze out a bit of memory from something I don't use.

On my HD install it always starts by default, and I want to disable it, but I can't find the call to it in the startup sequence anywhere.

Posted by mikshaw on Feb. 23 2007,07:47
Backgrounding X isn't an ideal thing to do as a default, in my opinion.
On the other hand, having multiple virtual terminals available is standard on most distros, and is my preferred way to run the system, but DSL typically runs only one. You can change this by modifying /etc/inittab

Posted by Wittfella on Feb. 23 2007,09:24
Quote
but DSL typically runs only one

That's why I asked, it's there, you just can't use it without the mod.

Quote
Backgrounding X isn't an ideal thing to do

Can't say I'm experienced enough with linux to fully understand the implications, but from my testing there appears to be no difference from the gui point of view, and it seems to happily swap F1 to F2 back and forth.

Posted by mikshaw on Feb. 23 2007,15:10
I didn't mean to imply that you were doing anything wrong, it's just that backgrounding an application like X, and then running other tasks in the same virtual terminal, may interfere with what you're doing. Any messages printed from X or applications running in X that aren't being redirected will be printed to your terminal (as I understand it, anyway), and may interfere with what you are doing in the terminal. It probably won't cause problems, but may be distracting.
Posted by curaga on Feb. 23 2007,15:17
Syslogd is started in /opt/bootlocal.sh which is the last thing that gets loaded before the login prompt on hd install. And X is by default started in tty1.

And to a suggestion: in hd-install, why other tty's than 1 also start x after loggin in? That's what desktops are for.. Roberts, more stuff for you to do, the default behavior could be changed here to start x on tty1, but console on others..

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.