On Mon, 2006-08-14 at 22:06 +0200, Andrea Borgia wrote: > > I think the best thing to do is to stop interfering with > > jabber/jabber-common, and create a separate user to run pymsnt. > > A separate unprivileged user might be a good idea anyway, but I am > unsure how that would help with respect to the log issue. > > I see two possible solutions here: > > 1) convince the maintainers of jabber to explicitly list the log files > in the logrotate config file so their config won't match your log > > 2) place pymsnt's logfile somewhere else
> No.1 appears reasonable if you plan tighter integration with the main > packages, otherwise no.2 sounds like a plan. In retrospect I think my decision to rely on jabber-common to provide the infrastructure for the package was a bad idea. I did it because I was inexperienced with Debian packaging at the time. Nowadays I know much better, and this fact, combined with the lack of activity on the jabber/jabber-common front _and_ the fact that the package is now going into Debian proper made me decide that I should do the job properly and give pymsnt its own user and log directory. BTW, if you want to quell the messages from logrotate but don't want to wait a few days for version 1.11.1-5 of the package to show up in unstable, you can grab the source package from <http://mentors.debian.net/>. PS - thanks for noticing this bug in the first place! > Andrea. -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
