Ramdrive: /var/log/z-way-server.log

[fableman]

When you got lots of sensors you get alot of access on the: /var/log/z-way-server.log
Iam thinking of moving the /var/log/z-way-server.log to a ram drive to make the SD card to live longer.

Is it a good or bad idee? I don't know how important the .log file is for the server, and I got some plans to make my own alet system using perl and the .log file and prowl

config.xml:
<config>
<automation-dir>automation</automation-dir>
<log-file>/var/log/z-way-server.log</log-file>
<log-level>0</log-level>
<debug-port></debug-port>
</config>

[pofs]

You can actually use syslog daemon for logging, and configure it to write wherever you want (remote database, socket, log server, etc.)
To do so, specify "syslog" instead of log file name.

[fableman]

Dose the raz need the log file it self?

If it messup will it break any function?

[pofs]

Log is just for diagnostics, RaZberry can work fine without it.

[fableman]

Thanks! I will build my own alarm app using python and scan the .log and send out alarms using prowl (better then some russian sms service or email. )

[pz1]

You can actually use syslog daemon for logging, and configure it to write wherever you want (remote database, socket, log server, etc.)
To do so, specify "syslog" instead of log file name.

I am testing this on Synology syslog server. It works more or less. In the beginning I was loosing many messages. You need to adapt Raspberry /etc/rsyslog.conf in several places. I've deleted all the lines after RULES, and added the red lines.

# /etc/rsyslog.conf Configuration file for rsyslog.
#
# For more information see
# /usr/share/doc/rsyslog-doc/html/rsyslog_conf.html


#################
#### MODULES ####
#################

$ModLoad imuxsock # provides support for local system logging
$ModLoad imklog # provides kernel logging support
#$ModLoad immark # provides --MARK-- message capability

# Remove rate limit
$SystemLogRateLimitInterval 0


# provides UDP syslog reception
#$ModLoad imudp
#$UDPServerRun 514

# provides TCP syslog reception
#$ModLoad imtcp
#$InputTCPServerRun 514


###########################
#### GLOBAL DIRECTIVES ####
###########################

#
# Use traditional timestamp format.
# To enable high precision timestamps, comment out the following line.
#
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat

#
# Set the default permissions for all log files.
#
#$FileOwner root
#$FileGroup adm
$FileCreateMode 0640
$DirCreateMode 0755
$Umask 0022

#
# Where to place spool and state files
#
$WorkDirectory /var/spool/rsyslog

#
# Include all config files in /etc/rsyslog.d/
#
$IncludeConfig /etc/rsyslog.d/*.conf


###############
#### RULES ####
###############

*.* @192.168.1.33

[fableman]

Thanks..

For starter I will just put it on a ramdrive (on the rasberry) to speed it up and stop the .log from tearing the SD card.

[pz1]

I am testing this on Synology syslog server.

Not really happy with this yet. Principle seems OK, but gives a lot of traffic > 2000 log messages per second in bursts. Logs don't read nicely either (wrong order for me). Maybe syslog server for newer Synology OS are better.