Package: mailman
Version: 1:2.1.11-11
Severity: minor
p...@mail:~$ ps -fe | grep find
root 6846 5473 9 12:50 pts/0 00:00:39 find /var/lib/mailman/ -type d
-exec chmod g+s {} ;
paul 11875 31817 0 13:01 pts/48 00:00:00 grep find
It's still running. Ah, at 13:03 it's done.
Now we do have a rather large archive, however at first I thought that
something was hanging, as there's no indication that this find is
running; at the least a message such as "now fixing directory
permissions" would help.
Apart from the fact that:
find /var/lib/mailman/ -type d -print0 | xargs -0 --no-run-if-empty chmod g+s
is more efficient, is there an expectation that the permissions may have
become wrong somehow during the months mailman was running? If so, isn't
a cron job to take care of this more appropriate? If not, why do this
upon a simple upgrade from 1:2.1.11-2 -> 1:2.1.11-11 ?
Running it in the background would have been best.
I;m just happy that apache was not also upgraded at the same time, as it
probably would have been stopped during this whole time. That would have
sucked.
thanks,
Paul Slootman
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
