On Wed, 22 Jan 2014, Dave Neary wrote: that device was reporting a full disk transiently I know mailman quite well -- Russ herrold

On Wed, 22 Jan 2014, Dave Neary wrote: * nod * A couple of thoughts as to 'doing mailman' better: zero: Set the moderator auto-discard queue to seven days and be done with it -- on a geek mailing list, people 'get it' that they have to subscribe to post, and will get the customary notices when they mess up. Dump the clutter, as mailman has .. very weak ... logging in its v 2 series one: To permit us to ID this going forward, please install 'diskcheck' on the unit, and optionally tune it to emit notices to the mailing list or some monitored place ftp://ftp.owlriver.com/pub/mirror/ORC/diskcheck/ builds trivially, and is no arch with no unusual BR or Reqs config file is: /etc/diskcheck.conf and looks to use the sourced value for mailTo and possibly set it to the global mailman owner, or the infra list owner, or (a poorer choice) the list I also tinker with the value for: mailFrom to make it easier to 'see' these with procmail locally filtering stuff two: it may make sense to set the MTA up to use a custom find script looking at the outbound queue, and deleting undeliverables after a day or two (the content of a mailing list is 'bulk' and should not be 'critical' for delivery as it is routine and archived into a pipermail archive. After cleaning the OB queue, restart the MTA for hood measure, and optionally the mailman as well third: Via cron, I run a monthly process to enumerate all the mailing lists on a given host, and then to dump an email with all subscribers, and to pull off various stats. It is built from simple mailman CLI tools. I save the detail over time, and can sometimes help former members back onto the lsit, or figure out my subscribers count more easily [root@lists cron.monthly]# cat manifest-mailman.sh #!/bin/sh # # /root/bin/manifest-mailman.sh # # cd /etc/cron.monthly # ln -s /root/bin/manifest-mailman.sh # export PATH='/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin' # TMPFILE="/root/tmp/mailmanlist" TMPDIR=`dirname $TMPFILE` [ ! -d $TMPDIR ] && mkdir -p $TMPDIR cd /usr/lib/mailman/bin for i in `./list_lists | grep -v ^[0-1] | awk {'print $1'}`; do echo "$i " > ./list_members $i > echo " " >done # cat $TMPFILE | mail -s "ELIDED mailman list members" root [ -e $TMPFILE ] && rm -f $TMPFILE # [root@lists cron.monthly]# fourth: (personal) I had built a 'herrold.pp' in my local git CO, but forget what I need to do to get it applied, and my google fu on the ovirt site fails me[herrold@centos-6 ovirt]$ cat \ ./git/infra-puppet/infra-puppet/modules/ovirt_inmanifests/user/herrold.pp # The user for Russ Herrold class ovirt_infra::user::herrold($password = undef) { ovirt_infra::user {'herrold': key => 'ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAoN/a499NclkAk9XIYSh6SQlCZNGgHIM3nDoYjc9ul4tTzticF8r/UmZXiQa/rnAi8Z9TWgDZ5w+RfUOCSCW38ndwR7v4ji7uvQ0v38ZKBOomjIYxDzVPBLq6iorDSO+Yph3P7oBzsqsRuNBgEOYxIx8vz8KQcqzFUhyWNGWyLLWPCbuKjmBwZS1HiNMdJUlKuRUe/KMmLW2bOEKpf9p2KaxsVjf9yuYqs8fyAoDbcfveEp3+E5i7DLc9H/9rBX99wq2IgwpZPkwUJU41e6Lauhc9lXMvnlCEtud3cnctpBa9U5a9cS1TJIJNLiA05nuiQdij0tvUHTv4zn8SgwBzZQ== herrold(a)owlriver.com', password => $password, } } I assume there is a way I can leverage one of my ovirt credentials to get it 'reviewed' and committed -- possibly get seek a gerrit review of it? Please remind me if you could. Thanks -- Russ herrold