[FUG-BR] Logfile turned over
Airton Arantes
airton.arantes em gmail.com
Quarta Maio 18 10:03:28 BRT 2011
Olá pessoal, estou montando um servidor de logs, syslogd, em um FBSD8.2.
Enquanto estava trabalhando, vi que o meu arquivo /var/log/messages mostrou
uma mensagem assim:
logfile turned over due to size>100K
Fiz algumas pesquisas nessa e em outras listas, mas não consegui nenhuma
descrição mais precisa sobre isso. Editei o arquivo /etc/newsyslog.conf para
permitir o tamanho do arquivo messages ser maior do que 100K, restartei os
serviços syslogd e newsyslog, mas o meu /var/log/messages permanece do mesmo
jeito.
Segue abaixo o meu arquivo /etc/newsyslog.conf e /etc/syslogd.conf
# configuration file for newsyslog
# $FreeBSD: src/etc/newsyslog.conf,v 1.52.2.1.6.1 2010/12/21 17:09:25
kensmith Exp $
#
# Entries which do not specify the '/pid_file' field will cause the
# syslogd process to be signalled when that log file is rotated. This
# action is only appropriate for log files which are written to by the
# syslogd process (ie, files listed in /etc/syslog.conf). If there
# is no process which needs to be signalled when a given log file is
# rotated, then the entry for that file should include the 'N' flag.
#
# The 'flags' field is one or more of the letters: BCGJNUWZ or a '-'.
#
# Note: some sites will want to select more restrictive protections than the
# defaults. In particular, it may be desirable to switch many of the 644
# entries to 640 or 600. For example, some sites will consider the
# contents of maillog, messages, and lpd-errs to be confidential. In the
# future, these defaults may change to more conservative ones.
#
# logfilename [owner:group] mode count size when flags
[/pid_file] [sig_num]
/var/log/all.log 600 7 * @T00 J
/var/log/amd.log 644 7 100 * J
/var/log/auth.log 600 7 100 * JC
/var/log/console.log 600 5 100 * J
/var/log/cron 600 3 100 * JC
/var/log/daily.log 640 7 * @T00 JN
/var/log/debug.log 600 7 100 * JC
/var/log/kerberos.log 600 7 100 * J
/var/log/lpd-errs 644 7 100 * JC
/var/log/maillog 640 7 * @T00 JC
/var/log/messages 644 5 500 * JC *#Aqui
eu mudei de 100 para 500*
/var/log/monthly.log 640 12 * $M1D0 JN
/var/log/pflog 600 3 100 * JB
/var/run/pflogd.pid
/var/log/ppp.log root:network 640 3 100 * JC
/var/log/security 600 10 100 * JC
/var/log/sendmail.st 640 10 * 168 B
/var/log/weekly.log 640 5 1 $W6D0 JN
/var/log/wtmp 644 3 * @01T05 B
/var/log/xferlog 600 7 100 * JC
# $FreeBSD: src/etc/syslog.conf,v 1.30.2.1.6.1 2010/12/21 17:09:25 kensmith
Exp $
#
# Spaces ARE valid field separators in this file. However,
# other *nix-like systems still insist on using tabs as field
# separators. If you are sharing this file between systems, you
# may want to use only tabs as field separators here.
# Consult the syslog.conf(5) manpage.
+192.168.0.14
*.*
/var/log/log_remote/ZabbixServer/zabbix.log
+100.100.90.20
*.*
/var/log/log_remote/Firewall/FirewallSede.log
#Extreme Aloo Sede
+201.200.200.200
*.*
/var/log/log_remote/Extreme/Extreme.log
+192.168.0.11
*.* /var/log/cactiServer.log
*.err;kern.warning;auth.notice;mail.crit /dev/console
*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err
/var/log/messages
security.* /var/log/security
auth.info;authpriv.info /var/log/auth.log
mail.info /var/log/maillog
lpr.info /var/log/lpd-errs
ftp.info /var/log/xferlog
cron.* /var/log/cron
*.=debug /var/log/debug.log
*.emerg *
# uncomment this to log all writes to /dev/console to /var/log/console.log
#console.info /var/log/console.log
# uncomment this to enable logging of all log messages to /var/log/all.log
# touch /var/log/all.log and chmod it to mode 600 before it will work
#*.* /var/log/all.log
# uncomment this to enable logging to a remote loghost named loghost
#*.* @loghost
# uncomment these if you're running inn
# news.crit /var/log/news/news.crit
# news.err /var/log/news/news.err
# news.notice /var/log/news/news.notice
!ppp
*.* /var/log/ppp.log
!*
--
Airton Arantes Coelho Filho
Mais detalhes sobre a lista de discussão freebsd