Is the the logrotate initialisation correct?

Hello,

I took a look at the logrotate initialisation because I need lot of logs right now to develop my app taking care to not fill up the available space.

But I saw that the config file is not /etc/logrotate.d/rsyslog but /etc/logrotate.d/syslog instead.
well ok maybe but in it, I can see:

 postrotate
    /etc/init.d/rsyslog reload 2> /dev/null || true
 endscript

But again there is no /etc/init.d/rsyslog but /etc/init.d/syslog instead and again in it I can see:

NAME=rsyslog
....
SCRIPTNAME=/etc/init.d/$NAME

So it’s confusing !?!

Alain

What about /etc/syslog-startup.conf ?

/etc/syslog-startup.conf is

DESTINATION=buffer      # log destinations (buffer file remote)
LOGFILE=/var/log/messages   # where to log (file)
REMOTE=loghost:514      # where to log (syslog remote)
REDUCE=no           # reduce-size logging
DROPDUPLICATES=no       # whether to drop duplicate log entries
#ROTATESIZE=0           # rotate log if grown beyond X [kByte]
#ROTATEGENS=3           # keep X generations of rotated logs
BUFFERSIZE=2000         # size of circular buffer [kByte]
FOREGROUND=no           # run in foreground (don't use!)
#LOGLEVEL=5         # local log level (between 1 and 8)

And so?

Hi AlBo,

Maybe I misunderstand the question? Would you please clarify?

I guess you are asking how to modify the log buffer size to save big log from your app?
If yes, then we can modify and increase the default “BUFFERSIZE”.

I’m surprised by the confusion referencing rsyslog in where the files are named syslog in several places.

Now, if busybox uses /etc/syslog-startup.conf it’s again more confusing to me. Why the usual configuration files are still here and finally what is actually used and not used?

Alain

Hi Alain,

Does this issue solved?
Do you have chance to test configure “/etc/syslog-startup.conf” and see what happen?

Thx