On Sun, Oct 31, 2010 at 08:30:23PM -0400, Yaroslav Halchenko wrote: Hi Yaroslav,
> Hi Zbyszek, > > thanks for looking into it ... Thanks for the quick reply :) > action.d/mynetwatchman.conf changes -- should be ok This parts is still valid... > action.d/mail-buffered.conf -- I don't think it would work... ...but the other three won't work indeed. (I had some strange notion that the mktemp would get executed tmpdir variable initialization, but it just gets substituted into the final command like you said. > > > +tmpdir = `mktemp --directory --suffix=-f2ban-dshield` > > +tmpfile = <tmpdir>/dshield > > since this is just a Python config file, it would simply substitute > `mktemp --directory --suffix=-f2ban-dshield`/dshield > for every occurrence of <tmpfile> which would be not what is desired... > am I correct? > > > as a generic and simple resolution, I think, tmpfiles should simply be > created under /var/run/fail2ban which belongs to root. I think there > was some discussion in some other bugreport... or it is deja vu Yes, this is a much better solution! Is the /var/run/fail2ban/ directory exported as a variable so it can be used in action rules without hardcoding the path? > agreed? Yeah, sorry for posting a complete untested patch ;( -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
