March 12, 201115 yr Mar 12 04:40:01 Tower syslogd 1.4.1: restart. Mar 12 05:35:55 Tower emhttp: shcmd (85): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 06:15:17 Tower emhttp: shcmd (86): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 06:36:01 Tower emhttp: shcmd (87): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 07:36:04 Tower emhttp: shcmd (88): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 08:36:01 Tower emhttp: shcmd (89): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 09:15:25 Tower emhttp: shcmd (90): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 09:36:10 Tower emhttp: shcmd (91): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 10:35:54 Tower emhttp: shcmd (92): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 11:36:00 Tower emhttp: shcmd (93): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 12:35:54 Tower emhttp: shcmd (94): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 14:00:55 Tower in.telnetd[20334]: connect from 192.168.3.131 (192.168.3.131) (Routine) Mar 12 14:00:57 Tower login[20335]: ROOT LOGIN on `pts/0' from `192.168.3.131' (Logins) Tower login: root Linux 2.6.32.9-unRAID. root@Tower:~# uptime 14:05:58 up 1 day, 22:51, 1 user, load average: 0.77, 0.98, 0.77 root@Tower:~# 14:05:58 up 1 day, 22:51, 1 user, load average: 0.77, 0.98, 0.77 v4.7 Pro I read on a search for this topic that "syslog will truncate after 1M". Does that mean it clears whatever log is existing and then start over anew?
March 12, 201115 yr Mar 12 04:40:01 Tower syslogd 1.4.1: restart. Mar 12 05:35:55 Tower emhttp: shcmd (85): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 06:15:17 Tower emhttp: shcmd (86): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 06:36:01 Tower emhttp: shcmd (87): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 07:36:04 Tower emhttp: shcmd (88): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 08:36:01 Tower emhttp: shcmd (89): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 09:15:25 Tower emhttp: shcmd (90): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 09:36:10 Tower emhttp: shcmd (91): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 10:35:54 Tower emhttp: shcmd (92): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 11:36:00 Tower emhttp: shcmd (93): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 12:35:54 Tower emhttp: shcmd (94): /usr/sbin/hdparm -y /dev/hda >/dev/null (Drive related) Mar 12 14:00:55 Tower in.telnetd[20334]: connect from 192.168.3.131 (192.168.3.131) (Routine) Mar 12 14:00:57 Tower login[20335]: ROOT LOGIN on `pts/0' from `192.168.3.131' (Logins) Tower login: root Linux 2.6.32.9-unRAID. root@Tower:~# uptime 14:05:58 up 1 day, 22:51, 1 user, load average: 0.77, 0.98, 0.77 root@Tower:~# 14:05:58 up 1 day, 22:51, 1 user, load average: 0.77, 0.98, 0.77 v4.7 Pro I read on a search for this topic that "syslog will truncate after 1M". Does that mean it clears whatever log is existing and then start over anew? The syslog files are "rotated" syslog is moved to syslog.1 syslog.1 is moved to syslog.2 a new syslog is then created and subsequently filled.
Archived
This topic is now archived and is closed to further replies.