On Tue, Mar 08, 2011 at 02:16:08AM +0100, Pau Garcia i Quiles wrote: > On Sun, Mar 6, 2011 at 9:42 PM, Kurt Roeckx <k...@roeckx.be> wrote: > > Package: src:witty > > Version: 3.1.2-3 > > > > Hi, > > > > There doesn't seem to be any package creating the /var/run/wt dir. > > This bugreport is actually wrong and the most appropriate action would > be to close it with a WONTFIX because witty itself does not require > /var/run/wt (the packages only provide libraries and the source for > the examples, no binaries). > > Instead of doing that, I will document who should create /var/run/wt, > why and when. I already wrote about that in August 2009 in the Wt > mailing list ( > http://www.mail-archive.com/witty-interest@lists.sourceforge.net/msg02065.html > ).
Having read the archive, I'd argue that using /var/run/apache2/wt would be the best solution for my case. (I'm using fcgi with apache2.) I assume nothing is trying to create either path currently. I think /tmp/wt is a bad idea. So it looks like that I need to create/modify some init script to create a directory in any case. I'm not sure that trying to create a directory other than the one from the config file is a good idea. But I think the library should try to create it the one from the config file if it doesn't exist yet. I could point it to a place where it can write in that case and I wouldn't have to modify any init scripts. It might also be a good idea if the library gave a proper warning message in that case, possibly suggesting /var/run/apache2/wt if running under apache. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
