Re: [Mailman-Users] Logging question...
Richard Barrett said: > Looking at your listing for the logs directory, most of the files are not > group writable. My guess is that is why not a whole lot is being written > to them. Hmm. Good point. I just updated newsyslog.conf. I must have typo'd that :-/ > I note that only the bounce, error and mischief logs are group writable > and those seem have some contents. And coincidentially they had 664 in newsyslog.conf :-/ > and the logs directory has the following permissions > > drwxrwsr-x3 mailman mailman 4608 Jun 17 00:45 logs So does mine.. > I think the set gid on the directory keeps everything in order as log > rotation is done. > > I confess I am surprised that check_perms did not find any problems. It > may be worth setting the permissions by hand and seeing if that makes any > difference. I just set them.. *crosses fingers* :) > btw: what are you using to do your log rotation. I'm using newsyslog, now with the following new entries: # Adding mailman logs # 1/3/2003, ges # Changed 6/17 due to screwup --ges /usr/local/mailman/logs/debug www:mailman 664 7 100 @T00 Z /usr/local/mailman/logs/digest mailman:mailman 664 7 100 @T00 Z /usr/local/mailman/logs/error mailman:mailman 664 7 100 @T00 Z /usr/local/mailman/logs/mischief mailman:mailman 664 7 100 @T00 Z /usr/local/mailman/logs/postmailman:mailman 664 7 100 @T00 Z /usr/local/mailman/logs/qrunner mailman:mailman 664 7 100 @T00 Z /usr/local/mailman/logs/smtpmailman:mailman 664 7 100 @T00 Z /usr/local/mailman/logs/subscribe www:mailman 664 7 100 @T00 Z /usr/local/mailman/logs/vette mailman:mailman 664 7 100 @T00 Z Thanks! Glenn --- The original portions of this message are the copyright of the author (c)1998-2002 Glenn E. Sieb.ICQ UIN: 300395IRC Nick: Rainbear "All acts of Love and Pleasure are Her rituals"-Charge of the Goddess -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Logging question...
At 22:39 17/06/2003, Glenn Sieb wrote: Richard Barrett said: > Usually 0664 for the files in $prefix/logs but the best way to get this > right is by running '$prefix/bin/check_perms -f' as either root or the > mailman user. This makes sure the setgid bit on directories are also > correct. I usually stop mailmanctl and the local MTA while check_perms is > doing its fix thing. Hey Richard! Thanks for the reply :) I did the check_perms -f (twice for good measure), and it found nothing... But why would my logs be empty? Are there directives in mm_cfg.py that I'm missing, perchance? The only logs that have anything are bounce (that was back in May) and error.1.gz (which was an apachectl stop/startssl) Glenn Looking at your listing for the logs directory, most of the files are not group writable. My guess is that is why not a whole lot is being written to them. I note that only the bounce, error and mischief logs are group writable and those seem have some contents. _All_ the files in my MM log directory have the following permissions: -rw-rw-r--1 mailman mailman 72692 Jun 17 22:37 post and the logs directory has the following permissions drwxrwsr-x3 mailman mailman 4608 Jun 17 00:45 logs I think the set gid on the directory keeps everything in order as log rotation is done. I confess I am surprised that check_perms did not find any problems. It may be worth setting the permissions by hand and seeing if that makes any difference. btw: what are you using to do your log rotation. Richard Thanks! Glenn (an ls -l of /usr/local/mailman/logs:) -rw-rw-r-- 1 mailman mailman 94981 May 8 21:13 bounce -rw-rw-r-- 1 mailman mailman 3681 Jun 17 16:59 error -rw-rw-r-- 1 mailman mailman102 Jun 17 00:00 error.0.gz -rw-rw-r-- 1 mailman mailman 1270 Jun 16 00:00 error.1.gz -rw-rw-r-- 1 mailman mailman 98 Jun 15 00:00 error.2.gz -rw-rw-r-- 1 mailman mailman 97 Jun 14 00:00 error.3.gz -rw-rw-r-- 1 mailman mailman 98 Jun 13 00:00 error.4.gz -rw-rw-r-- 1 mailman mailman 99 Jun 12 00:00 error.5.gz -rw-rw-r-- 1 mailman mailman 99 Jun 11 00:00 error.6.gz -rw-rw-r-- 1 mailman mailman100 Jun 10 00:00 error.7.gz -rw-rw-r-- 1 mailman mailman 63 Jun 17 00:00 mischief -rw-rw-r-- 1 mailman mailman105 Jun 17 00:00 mischief.0.gz -rw-rw-r-- 1 mailman mailman179 Jun 16 00:00 mischief.1.gz -rw-rw-r-- 1 mailman mailman101 Jun 15 00:00 mischief.2.gz -rw-rw-r-- 1 mailman mailman190 Jun 14 00:00 mischief.3.gz -rw-rw-r-- 1 mailman mailman101 Jun 13 00:00 mischief.4.gz -rw-rw-r-- 1 mailman mailman102 Jun 12 00:00 mischief.5.gz -rw-rw-r-- 1 mailman mailman168 Jun 11 00:00 mischief.6.gz -rw-rw-r-- 1 mailman mailman103 Jun 10 00:00 mischief.7.gz -rw-r--r-- 1 mailman mailman 63 Jun 17 00:00 post -rw-r--r-- 1 mailman mailman101 Jun 17 00:00 post.0.gz -rw-r--r-- 1 mailman mailman 98 Jun 16 00:00 post.1.gz -rw-r--r-- 1 mailman mailman 97 Jun 15 00:00 post.2.gz -rw-r--r-- 1 mailman mailman 96 Jun 14 00:00 post.3.gz -rw-r--r-- 1 mailman mailman 97 Jun 13 00:00 post.4.gz -rw-r--r-- 1 mailman mailman 98 Jun 12 00:00 post.5.gz -rw-r--r-- 1 mailman mailman 98 Jun 11 00:00 post.6.gz -rw-r--r-- 1 mailman mailman 99 Jun 10 00:00 post.7.gz -rw-r--r-- 1 mailman mailman 1056 Jun 17 16:59 qrunner -rw-r--r-- 1 mailman mailman104 Jun 17 00:00 qrunner.0.gz -rw-r--r-- 1 mailman mailman101 Jun 16 00:00 qrunner.1.gz -rw-r--r-- 1 mailman mailman100 Jun 15 00:00 qrunner.2.gz -rw-r--r-- 1 mailman mailman 99 Jun 14 00:00 qrunner.3.gz -rw-r--r-- 1 mailman mailman100 Jun 13 00:00 qrunner.4.gz -rw-r--r-- 1 mailman mailman101 Jun 12 00:00 qrunner.5.gz -rw-r--r-- 1 mailman mailman101 Jun 11 00:00 qrunner.6.gz -rw-r--r-- 1 mailman mailman102 Jun 10 00:00 qrunner.7.gz -rw-r--r-- 1 mailman mailman 63 Jun 17 00:00 smtp -rw-r--r-- 1 mailman mailman101 Jun 17 00:00 smtp.0.gz -rw-r--r-- 1 mailman mailman 98 Jun 16 00:00 smtp.1.gz -rw-r--r-- 1 mailman mailman 97 Jun 15 00:00 smtp.2.gz -rw-r--r-- 1 mailman mailman 96 Jun 14 00:00 smtp.3.gz -rw-r--r-- 1 mailman mailman 97 Jun 13 00:00 smtp.4.gz -rw-r--r-- 1 mailman mailman 98 Jun 12 00:00 smtp.5.gz -rw-r--r-- 1 mailman mailman 98 Jun 11 00:00 smtp.6.gz -rw-r--r-- 1 mailman mailman 99 Jun 10 00:00 smtp.7.gz -rw-r--r-- 1 www mailman 63 Jun 17 00:01 subscribe -rw-r--r-- 1 www mailman106 Jun 17 00:01 subscribe.0.gz -rw-r--r-- 1 www mailman103 Jun 16 00:01 subscribe.1.gz -rw-r--r-- 1 www mailman102 Jun 15 00:01 subscribe.2.gz -rw-r--r-- 1 www mailman101 Jun 14 00:01 subscribe.3.gz -rw-r--r-- 1 www mailman102 Jun 13 00:01 subscribe.4.gz -rw-r--r-- 1 www mailman103 Jun 12 00:01 subscribe.5.gz -rw-r--r-- 1 www mailman103 Jun 11 00:01 subscribe.6.gz -rw-r--r-- 1 www mailman
Re: [Mailman-Users] Logging question...
Richard Barrett said: > Usually 0664 for the files in $prefix/logs but the best way to get this > right is by running '$prefix/bin/check_perms -f' as either root or the > mailman user. This makes sure the setgid bit on directories are also > correct. I usually stop mailmanctl and the local MTA while check_perms is > doing its fix thing. Hey Richard! Thanks for the reply :) I did the check_perms -f (twice for good measure), and it found nothing... But why would my logs be empty? Are there directives in mm_cfg.py that I'm missing, perchance? The only logs that have anything are bounce (that was back in May) and error.1.gz (which was an apachectl stop/startssl) Thanks! Glenn (an ls -l of /usr/local/mailman/logs:) -rw-rw-r-- 1 mailman mailman 94981 May 8 21:13 bounce -rw-rw-r-- 1 mailman mailman 3681 Jun 17 16:59 error -rw-rw-r-- 1 mailman mailman102 Jun 17 00:00 error.0.gz -rw-rw-r-- 1 mailman mailman 1270 Jun 16 00:00 error.1.gz -rw-rw-r-- 1 mailman mailman 98 Jun 15 00:00 error.2.gz -rw-rw-r-- 1 mailman mailman 97 Jun 14 00:00 error.3.gz -rw-rw-r-- 1 mailman mailman 98 Jun 13 00:00 error.4.gz -rw-rw-r-- 1 mailman mailman 99 Jun 12 00:00 error.5.gz -rw-rw-r-- 1 mailman mailman 99 Jun 11 00:00 error.6.gz -rw-rw-r-- 1 mailman mailman100 Jun 10 00:00 error.7.gz -rw-rw-r-- 1 mailman mailman 63 Jun 17 00:00 mischief -rw-rw-r-- 1 mailman mailman105 Jun 17 00:00 mischief.0.gz -rw-rw-r-- 1 mailman mailman179 Jun 16 00:00 mischief.1.gz -rw-rw-r-- 1 mailman mailman101 Jun 15 00:00 mischief.2.gz -rw-rw-r-- 1 mailman mailman190 Jun 14 00:00 mischief.3.gz -rw-rw-r-- 1 mailman mailman101 Jun 13 00:00 mischief.4.gz -rw-rw-r-- 1 mailman mailman102 Jun 12 00:00 mischief.5.gz -rw-rw-r-- 1 mailman mailman168 Jun 11 00:00 mischief.6.gz -rw-rw-r-- 1 mailman mailman103 Jun 10 00:00 mischief.7.gz -rw-r--r-- 1 mailman mailman 63 Jun 17 00:00 post -rw-r--r-- 1 mailman mailman101 Jun 17 00:00 post.0.gz -rw-r--r-- 1 mailman mailman 98 Jun 16 00:00 post.1.gz -rw-r--r-- 1 mailman mailman 97 Jun 15 00:00 post.2.gz -rw-r--r-- 1 mailman mailman 96 Jun 14 00:00 post.3.gz -rw-r--r-- 1 mailman mailman 97 Jun 13 00:00 post.4.gz -rw-r--r-- 1 mailman mailman 98 Jun 12 00:00 post.5.gz -rw-r--r-- 1 mailman mailman 98 Jun 11 00:00 post.6.gz -rw-r--r-- 1 mailman mailman 99 Jun 10 00:00 post.7.gz -rw-r--r-- 1 mailman mailman 1056 Jun 17 16:59 qrunner -rw-r--r-- 1 mailman mailman104 Jun 17 00:00 qrunner.0.gz -rw-r--r-- 1 mailman mailman101 Jun 16 00:00 qrunner.1.gz -rw-r--r-- 1 mailman mailman100 Jun 15 00:00 qrunner.2.gz -rw-r--r-- 1 mailman mailman 99 Jun 14 00:00 qrunner.3.gz -rw-r--r-- 1 mailman mailman100 Jun 13 00:00 qrunner.4.gz -rw-r--r-- 1 mailman mailman101 Jun 12 00:00 qrunner.5.gz -rw-r--r-- 1 mailman mailman101 Jun 11 00:00 qrunner.6.gz -rw-r--r-- 1 mailman mailman102 Jun 10 00:00 qrunner.7.gz -rw-r--r-- 1 mailman mailman 63 Jun 17 00:00 smtp -rw-r--r-- 1 mailman mailman101 Jun 17 00:00 smtp.0.gz -rw-r--r-- 1 mailman mailman 98 Jun 16 00:00 smtp.1.gz -rw-r--r-- 1 mailman mailman 97 Jun 15 00:00 smtp.2.gz -rw-r--r-- 1 mailman mailman 96 Jun 14 00:00 smtp.3.gz -rw-r--r-- 1 mailman mailman 97 Jun 13 00:00 smtp.4.gz -rw-r--r-- 1 mailman mailman 98 Jun 12 00:00 smtp.5.gz -rw-r--r-- 1 mailman mailman 98 Jun 11 00:00 smtp.6.gz -rw-r--r-- 1 mailman mailman 99 Jun 10 00:00 smtp.7.gz -rw-r--r-- 1 www mailman 63 Jun 17 00:01 subscribe -rw-r--r-- 1 www mailman106 Jun 17 00:01 subscribe.0.gz -rw-r--r-- 1 www mailman103 Jun 16 00:01 subscribe.1.gz -rw-r--r-- 1 www mailman102 Jun 15 00:01 subscribe.2.gz -rw-r--r-- 1 www mailman101 Jun 14 00:01 subscribe.3.gz -rw-r--r-- 1 www mailman102 Jun 13 00:01 subscribe.4.gz -rw-r--r-- 1 www mailman103 Jun 12 00:01 subscribe.5.gz -rw-r--r-- 1 www mailman103 Jun 11 00:01 subscribe.6.gz -rw-r--r-- 1 www mailman242 Jun 10 00:01 subscribe.7.gz -rw-r--r-- 1 mailman mailman 63 Jun 17 00:01 vette -rw-r--r-- 1 mailman mailman102 Jun 17 00:01 vette.0.gz -rw-r--r-- 1 mailman mailman 99 Jun 16 00:01 vette.1.gz -rw-r--r-- 1 mailman mailman 98 Jun 15 00:01 vette.2.gz -rw-r--r-- 1 mailman mailman 97 Jun 14 00:01 vette.3.gz -rw-r--r-- 1 mailman mailman 98 Jun 13 00:01 vette.4.gz -rw-r--r-- 1 mailman mailman 99 Jun 12 00:01 vette.5.gz -rw-r--r-- 1 mailman mailman 99 Jun 11 00:01 vette.6.gz -rw-r--r-- 1 mailman mailman100 Jun 10 00:01 vette.7.gz --- The original portions of this message are the copyright of the author (c)1998-2002 Glenn E. Sieb.ICQ UIN: 300395IRC Nick: Rainbear "All acts of Love and Pleasure are Her rituals"-Charge of the Goddess -- Mailman-U
Re: [Mailman-Users] Logging question...
At 16:14 17/06/2003, Glenn Sieb wrote: Hey everyone.. running MM 2.1 on FreeBSD 4.8 with Postfix/AMaViS/SpamAssassin I had a user ask me why an email she sent never got posted to a list she's a proper member of.. so I went to investigate.. saw that yes, she indeed posted a message, it hit my SMTP, went through SA/AMaViS and through to Mailman, but it never went anywhere from there. So.. I went to look at the Mailman logs... they're um.. well.. empty. My guess is it is a perms thing... they're mostly owned by mailman:mailman with perms of 644, except for subscribe which is owned by www:mailman perms of 644 What are the proper permissions for the log files in /usr/local/mailman/logs? Usually 0664 for the files in $prefix/logs but the best way to get this right is by running '$prefix/bin/check_perms -f' as either root or the mailman user. This makes sure the setgid bit on directories are also correct. I usually stop mailmanctl and the local MTA while check_perms is doing its fix thing. Thank you! :) Glenn --- The original portions of this message are the copyright of the author (c)1998-2002 Glenn E. Sieb.ICQ UIN: 300395IRC Nick: Rainbear "All acts of Love and Pleasure are Her rituals"-Charge of the Goddess -- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
