Hello, I''m using datetime rules and as I am using the "localtz" keyword, I''m getting the following messages when shorewall starts: WARNING: --localtz is being replaced by --kerneltz, since "local" is ambiguous. Note the kernel timezone has caveats - see manpage for details. I guess that I am not the only one getting this message since I am not the only one running a kernel with revision 3.2.1. Replacing blindly "localtz" by "kerneltz" does not work as shorewall does not recognize this keyword. As I have not found any message related to shorewall on this particular subject, I was wondering if there was a way to fix this or if something was planned to fix it. I am looking forward for your answers, Thibault. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure
Hello Tom, I just saw your commit taking "kerneltz" into account. I''m using gentoo, and the latest stable ebuild is at revision 4.4.23 for now. I will certainly switch to an unstable version of the gentoo package in order to get your fix. Can you just tell me in which shorewall tag this commit was delivered ? Anyway, thanks a lot for being so responsive, Thibault On Mon, Mar 19, 2012 at 9:06 PM, Thibault Hild <thibault.hild@gmail.com> wrote:> Hello, > > I''m using datetime rules and as I am using the "localtz" keyword, I''m > getting the following messages when shorewall starts: > > WARNING: --localtz is being replaced by --kerneltz, since "local" is > ambiguous. Note the kernel timezone has caveats - see manpage for > details. > > I guess that I am not the only one getting this message since I am not > the only one running a kernel with revision 3.2.1. > Replacing blindly "localtz" by "kerneltz" does not work as shorewall > does not recognize this keyword. > As I have not found any message related to shorewall on this > particular subject, I was wondering if there was a way to fix this or > if something was planned to fix it. > > I am looking forward for your answers, > > Thibault.------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure
I did not read the commit until its end :-(. The fix will be part of shorewall 4.5.2... Sorry for interfering... On Sat, Mar 31, 2012 at 2:23 PM, Thibault Hild <thibault.hild@gmail.com> wrote:> Hello Tom, > > I just saw your commit taking "kerneltz" into account. > I''m using gentoo, and the latest stable ebuild is at revision 4.4.23 > for now. I will certainly switch to an unstable version of the gentoo > package in order to get your fix. > Can you just tell me in which shorewall tag this commit was delivered ? > > Anyway, thanks a lot for being so responsive, > > Thibault > > On Mon, Mar 19, 2012 at 9:06 PM, Thibault Hild <thibault.hild@gmail.com> wrote: >> Hello, >> >> I''m using datetime rules and as I am using the "localtz" keyword, I''m >> getting the following messages when shorewall starts: >> >> WARNING: --localtz is being replaced by --kerneltz, since "local" is >> ambiguous. Note the kernel timezone has caveats - see manpage for >> details. >> >> I guess that I am not the only one getting this message since I am not >> the only one running a kernel with revision 3.2.1. >> Replacing blindly "localtz" by "kerneltz" does not work as shorewall >> does not recognize this keyword. >> As I have not found any message related to shorewall on this >> particular subject, I was wondering if there was a way to fix this or >> if something was planned to fix it. >> >> I am looking forward for your answers, >> >> Thibault.------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure