DSM-G600, DNS-3xx and NSA-220 Hack Forum

Hi,

Normally you need something like:

ps -ef | grep syslogd

to get a line like:
2185 root     /ffp/sbin/syslogd -O /ffp/var/log/messages -s 1024 -b 1
telling you a syslogd is running.
However on the NAS running the ps command is running busybox in ps-mode.
No arguments are necessary. And as there aren't many processes running. A single ps is enough to search for the syslogd process.
However the above code "ps -ef | grep syslogd" also works.
If an output line contains "grep syslogd", this is not the syslogd process, but the grepping of the "ps -ef" output.

On my NAS the syslogd process is running because I've started myself using the a start script with the following code:

#!/ffp/bin/sh

# PROVIDES: my_syslogd

. /ffp/etc/ffp.subr

name="syslogd"
command="/ffp/sbin/syslogd"
arguments="-O /ffp/var/log/messages -s 1024 -b 1"
start_cmd="syslogd_start"
stop_cmd="syslogd_stop"

syslogd_start()
{
        echo "Starting syslogd"
        $command $arguments 1>/ffp/var/$name.log 2>/ffp/var/$name.log &
}

syslogd_stop()
{
        echo "Stopping syslogd"
        killall syslogd
}

run_rc_command "$1"

You can manually start it with:

/ffp/sbin/syslogd -O /ffp/var/log/messages -s 1024 -b 1 &

This creates as log file "/ffp/var/log/messages" of max 1Mb and rotates it to "/ffp/var/log/messages.0" if the 1Mb is full.

HTH.,

RSD76