Skip to content

Commit

Permalink
Move syslogd after network so we can log kernel messages to remote se…
Browse files Browse the repository at this point in the history
…rver

Since syslogd was started before the network was up, all syslog messages before the network was up were discarded and not send to the remoe syslog server. By moving the syslogd startup until after the network, the kernel boot messages are available on the central syslog.
  • Loading branch information
dagwieers committed Mar 9, 2013
1 parent 3d5d9bb commit 5ce4c9b
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,10 @@

source /var/config/settings.conf

SYSLOGD_OPTIONS="-L"
SYSLOGD_OPTIONS="-L -D"

if [ "$SYSLOG_REMOTE" == "true" -a "$SYSLOG_SERVER" ]; then
SYSLOGD_OPTIONS="$SYSLOGD_OPTIONS -R $SYSLOG_SERVER"
SYSLOGD_OPTIONS="-R $SYSLOG_SERVER $SYSLOGD_OPTIONS"
fi

if [ -f /storage/.config/syslog.conf ]; then
Expand Down

1 comment on commit 5ce4c9b

@MilhouseVH
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm guessing this change is responsible for the four network related messages that now appear when booting a Raspberry Pi (I'm booting over NFS, so boot=NFS=192.168.0.3 etc.).

I captured the image below from a video of my Pi booting with "progress" enabled - the four rpcbind lines always appear and are also visible to users when booting normally (ie. no progress). These lines shouldn't be displayed to the user, they could be confused with errors/warnings.

Pi_Boot_Syslog

Please sign in to comment.