Quote:
Originally Posted by Babelduo
I wasnt logged in into the server.
|
You don't need to, that's why you have cron jobs.
Quote:
Originally Posted by Babelduo
How can I find out more about what happend at this time
|
The problem is Linux doesn't come with extensive logging enabled to provide you with a full audit trail on installation. If you need it you have to configure it beforehand.
Quote:
Originally Posted by Babelduo
or which cron did this?
|
Recursively list and grep all cron job directories and crontab files (/etc/crontab, /etc/cron.*/, /var/cron/, /var/spool/cron, etc, etc) for any name or application hinting at any service checking or run the cron daemon in debug mode:
'/path/to/crond -x sch,proc,test' (or
'crond -x sch,proc,test 2>&1 | tee | while read LINE; do echo "$(/bin/date +'%b %d %H:%M:%S hostname') crondebug ${LINE}"; done | tee /var/log/cron.debug' if you want to correlate things a wee bit easier). Note you should only use the latter if from your auth.log entries you have determined it is a job running at a low interval and you should not use ",test" on systems where you can not afford to
not run jobs like production servers.
Quote:
Originally Posted by Babelduo
p.s: sry I wanted to put this into Security!
|
Yeah, but I'll find it anyway ;-p *Next time use the report button on your post to ask a moderator to move your thread for you.
