(I'll omit the big list of files generated at this point) less secure So to see what's been happening with users logging on to the system I would do somethnig like: cd ls Usually, there is a program like logrotate which periodically renames old files and deleted very old files (it may also compress files) from the log directory. 'man syslog' at the prompt).īy convention, the log files should be in a directory /var/log (/var/adm/log on some systems). (the links I've provided here are to documents which should already be available on your system - try typing, e.g. Syslogd's behaviour is configurable - the config file is usually /etc/nf The latter records messages generated from the kernel while the former records messages from programs. The same situation exists in Linux - there are 2 daemons which should be started when the system boots - syslogd and klogd. What you see in MSWindows Event Viewer are the messages logged by the system logging facility - there is nothing to prevent applications writing logs elsewhere (and sometimes there are good reasons for not using the system logging facilities). In Linux/Unix/Posix (but from here I'll just say 'Linux') all the logs are written as text files - so anything which reads text files can read the logs.
0 Comments
Leave a Reply. |