I think I may have a problem with probing on my ProFtpd server. The log files are showing: /USR/SBIN/CRON[7835]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 22 20:22:02 linux -- MARK -- Jan 22 20:42:02 linux -- MARK -- Jan 22 20:59:00 linux /USR/SBIN/CRON[7910]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 22 21:22:02 linux -- MARK -- Jan 22 21:42:02 linux -- MARK -- Jan 22 21:59:00 linux /USR/SBIN/CRON[7985]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 22 22:22:02 linux -- MARK -- Jan 22 22:42:02 linux -- MARK -- Jan 22 22:59:00 linux /USR/SBIN/CRON[8059]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 22 23:22:02 linux -- MARK -- Jan 22 23:42:02 linux -- MARK -- Jan 22 23:59:00 linux /USR/SBIN/CRON[8134]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 00:22:02 linux -- MARK -- Jan 23 00:42:02 linux -- MARK -- Jan 23 00:59:00 linux /USR/SBIN/CRON[8208]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 01:22:02 linux -- MARK -- Jan 23 01:42:02 linux -- MARK -- Jan 23 01:59:00 linux /USR/SBIN/CRON[8283]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 02:22:02 linux -- MARK -- Jan 23 02:42:02 linux -- MARK -- Jan 23 02:59:00 linux /USR/SBIN/CRON[8358]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 03:22:02 linux -- MARK -- Jan 23 03:42:02 linux -- MARK -- Jan 23 03:59:00 linux /USR/SBIN/CRON[8432]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 04:14:00 linux /USR/SBIN/CRON[8452]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.daily) Jan 23 04:42:02 linux -- MARK -- Jan 23 04:59:00 linux /USR/SBIN/CRON[8575]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 05:22:02 linux -- MARK -- Jan 23 05:42:03 linux -- MARK -- Jan 23 05:59:00 linux /USR/SBIN/CRON[8649]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 06:22:03 linux -- MARK -- Jan 23 06:42:03 linux -- MARK -- Jan 23 06:59:00 linux /USR/SBIN/CRON[8724]: (root) CMD ( rm -f /var/spool/cron/ I'm a newbie to linux, this is why I'm asking. Thanks as always
You mean all the "-- MARK --" entries? man syslogd: -m interval The syslogd logs a mark timestamp regularly. The default interval between two -- MARK -- lines is 20 minutes. This can be changed with this option. Setting the interval to zero turns it off entirely. Brad Dameron SeaTab Software www.seatab.com On Mon, 2005-01-24 at 14:02, a.bridge@insightbb.com wrote:
I think I may have a problem with probing on my ProFtpd server. The log files are showing:
/USR/SBIN/CRON[7835]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 22 20:22:02 linux -- MARK -- Jan 22 20:42:02 linux -- MARK -- Jan 22 20:59:00 linux /USR/SBIN/CRON[7910]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 22 21:22:02 linux -- MARK -- Jan 22 21:42:02 linux -- MARK -- Jan 22 21:59:00 linux /USR/SBIN/CRON[7985]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 22 22:22:02 linux -- MARK -- Jan 22 22:42:02 linux -- MARK -- Jan 22 22:59:00 linux /USR/SBIN/CRON[8059]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 22 23:22:02 linux -- MARK -- Jan 22 23:42:02 linux -- MARK -- Jan 22 23:59:00 linux /USR/SBIN/CRON[8134]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 00:22:02 linux -- MARK -- Jan 23 00:42:02 linux -- MARK -- Jan 23 00:59:00 linux /USR/SBIN/CRON[8208]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 01:22:02 linux -- MARK -- Jan 23 01:42:02 linux -- MARK -- Jan 23 01:59:00 linux /USR/SBIN/CRON[8283]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 02:22:02 linux -- MARK -- Jan 23 02:42:02 linux -- MARK -- Jan 23 02:59:00 linux /USR/SBIN/CRON[8358]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 03:22:02 linux -- MARK -- Jan 23 03:42:02 linux -- MARK -- Jan 23 03:59:00 linux /USR/SBIN/CRON[8432]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 04:14:00 linux /USR/SBIN/CRON[8452]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.daily) Jan 23 04:42:02 linux -- MARK -- Jan 23 04:59:00 linux /USR/SBIN/CRON[8575]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 05:22:02 linux -- MARK -- Jan 23 05:42:03 linux -- MARK -- Jan 23 05:59:00 linux /USR/SBIN/CRON[8649]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 23 06:22:03 linux -- MARK -- Jan 23 06:42:03 linux -- MARK -- Jan 23 06:59:00 linux /USR/SBIN/CRON[8724]: (root) CMD ( rm -f /var/spool/cron/
I'm a newbie to linux, this is why I'm asking.
Thanks as always
a.bridge wrote regarding '[SLE] Log File Entries' on Mon, Jan 24 at 16:02:
I think I may have a problem with probing on my ProFtpd server. The log files are showing:
/USR/SBIN/CRON[7835]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 22 20:22:02 linux -- MARK -- Jan 22 20:42:02 linux -- MARK -- Jan 22 20:59:00 linux /USR/SBIN/CRON[7910]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
[...]
I'm a newbie to linux, this is why I'm asking.
Oh crap, I've got it too! Jan 24 00:59:00 newwww /USR/SBIN/CRON[3551]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 24 01:59:00 newwww /USR/SBIN/CRON[11876]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 24 02:59:00 newwww /USR/SBIN/CRON[20231]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Actually, that's just cron cleaning up after itself. The script is coped into lastrun, run, and then removed. It's normal. The MARK lines are explained in the man page referred to in the other post - it's just to let a largely idle server (with regards to syslog activity) notify you that yes, the syslog daemon is still running. --Danny, who generally turns the mark interval down (or off)
Danny Sauer wrote:
a.bridge wrote regarding '[SLE] Log File Entries' on Mon, Jan 24 at 16:02:
I think I may have a problem with probing on my ProFtpd server. The log files are showing:
/USR/SBIN/CRON[7835]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 22 20:22:02 linux -- MARK -- Jan 22 20:42:02 linux -- MARK -- Jan 22 20:59:00 linux /USR/SBIN/CRON[7910]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
[...]
I'm a newbie to linux, this is why I'm asking.
Oh crap, I've got it too!
Jan 24 00:59:00 newwww /USR/SBIN/CRON[3551]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 24 01:59:00 newwww /USR/SBIN/CRON[11876]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 24 02:59:00 newwww /USR/SBIN/CRON[20231]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Actually, that's just cron cleaning up after itself. The script is coped into lastrun, run, and then removed. It's normal. The MARK lines are explained in the man page referred to in the other post - it's just to let a largely idle server (with regards to syslog activity) notify you that yes, the syslog daemon is still running.
--Danny, who generally turns the mark interval down (or off)
Thank you for the info
participants (4)
-
a.bridge＠insightbb.com -
Aaron Bridge
-
Brad Dameron -
Danny Sauer