Home / user-31462

user31462's questions

Martin Hope
user31462
Asked: 2010-02-16 09:23:12 +0800 CST
  • 1

What I have: VMware ESXi 4.0 with busybox installed. Among busybox applets, I'm interested in syslogd. By default, it's running as busybox syslogd. I can see it via ps ax:

ps ax | grep syslog
4316 4316 busybox              syslogd

What I need: To run syslogd with options. Like that:

busybox syslogd -R 10.30.35.67

My questions:

  1. How to configure busybox, so that -R options comes to play at system startup? Is there any config file or something like that?

  2. How to correctly change busybox syslogd options after the system has been started? How to stop busybox syslogd properly? How to start it with new options? I tried to kill busybox syslogd process (4316 in my case), but after restarting busybox syslogd -R 10.30.35.67 I can't see any syslogd-related process at all.

vmware-esxi vmware-esx syslog busybox
Martin Hope
user31462
Asked: 2010-02-09 07:04:34 +0800 CST
  • 4

Here is the system:

  • SUSE Linux Enterprise Server 10
  • syslog-ng with predefined syslog-ng.conf
  • messages in /var/log/messages look like:

Feb 8 09:29:53 sles1 sshd[17529]: Accepted keyboard-interactive/pam for root from 10.30.34.64 port 4855 ssh2

What I need:

  • to log event severity/facility. For instance, add <PRI> at the beginning of the message:

<15> Feb 8 09:29:53 sles1 sshd[17529]: Accepted keyboard-interactive/pam for root from 10.30.34.64 port 4855 ssh2

My question is:

How to change syslog-ng.conf to enable this kind of logging?

Thanks.

sles sles10 syslog-ng
Martin Hope
user31462
Asked: 2010-01-13 02:29:54 +0800 CST
  • 2

We develop a Linux application to work on different RedHat/SUSE distributions. This application (namely, daemon) is expected to be automatically run at startup so we place our startup script in /etc/init.d/ directory and create symlinks in runlevel directories (../rc.d/rc5.d/, for instance). If a user removes our application, our uninstall script removes all our stuff including symlinks. It works fine if OS doesn't provide parallel script running. If parallel running is enabled, we need another solution. For instance, in SLES 10, we have in /etc/sysconfig/boot:

# Run all scripts or rather start/stop all services
# which are independent from each other in parallel.

RUN_PARALLEL="yes"

As far as we understand, we have to register our script with insserv utility. In this case, the system analyzes a script header and creates/removes symlinks on it's own. If it's true, how to organize installation/uninstallation of our application to cover both parallel and sequential startup script running? It looks like we should behave differently when parallel running is disabled or enabled. In first case, we should care about symlinks ourselves. In second case, we should delegate it to insserv. Is this right approach? If it's true, should we analyze whether parallel running is enabled by checking /etc/sysconfig/boot? It looks unreliable because in different Linux distributionsit could be different location and different parameter.

What's the best practice for installation/uninstallation Linux application that covers both parallel and sequential system startup?

Thanks,

linux scripting installation