Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">The simplest Linux config files typically have formats that look something like this:<br/><div class="codeheader">Code:</div><div class="code"># how often (in minutes) data is saved when all interface are offline<br/>OfflineSaveInterval 30<br/><br/># force data save when interface status changes (1 = enabled, 0 = disabled)<br/>SaveOnStatusChange 1<br/><br/># file used for logging if UseLogging is set to 1<br/>LogFile "/var/log/vnstat.log"<br/><br/># file used as daemon pid / lock file<br/>PidFile "/var/run/vnstat.pid"</div>The standard extension, if there is one, is .conf. Hash (#) is the most common comment character by far. Semicolon (<img alt="Wink" border="0" src="/static/img/emoticons/wink.gif"/> and C-style comments crop up too.<br/><br/>I think a good, human-manipulatable config file that ISN'T part of the wallet would be a big step forward. There are a lot of options that are currently specified on the command line (noirc, for example, or -minimizetotray) which might be better specified in a config file.</div> text/html