<br><div class="gmail_quote">2010/10/20 Frédéric Bohé <span dir="ltr"></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
On mer., 2010-10-20 at 11:24 +0200, Arjen de Korte wrote:<br>
> Citeren Frederic BOHE <<a href="mailto:fbohe-guest@alioth.debian.org">fbohe-guest@alioth.debian.org</a>>:<br>
><br>
> > Author: fbohe-guest<br>
> > Date: Wed Oct 20 09:13:38 2010<br>
> > New Revision: 2588<br>
> > URL: <a href="http://trac.networkupstools.org/projects/nut/changeset/2588" target="_blank">http://trac.networkupstools.org/projects/nut/changeset/2588</a><br>
> ><br>
> > Log:<br>
> > Remove hack from confpath function. You have to declare a<br>
> > NUT_CONFPATH environnement variable in your Windows settings<br>
><br>
> This is not the intended use, it is only meant for people that wish to<br>
> override the build-in default value. Provide ./configure with the path<br>
> where the config files will be stored and most people will never have<br>
> to touch this.<br>
><br>
<br>
</div>Agree. But the question is : what is "the path where the config files<br>
will be stored" in a Windows environnement ? I am not sure how to handle<br>
this correctly right now. If you have any suggestion...<br></blockquote></div><br>good point: I'm still unsure about the best solution here!<br>- we could keep the unix way, which is the path nut has followed for years, by keeping config files. But the above question is still valid: where to put these data (c:\etc or). In all case, this is a configure param.<br>
- or we could have a more native windows approach, by having the conf stored in the registry. Though this needs to change the *conf implementation.<br><br>In both cases, I don't know if there is a better solution for addressing at the same time the security side of the config ...<br>
<br>Arno<br>