Hi Timo, You were good enough to add the -n flag to the dovecot command to output the current *changed* config parameters (changed as compared to the defaults) of the running dovecot process. This makes it much easier to troubleshoot issues - thanks! Another flag that postfix has is the -d flag (postconf -d). This one outputs all of the DEFAULTS of the current running postfix process/version. I just used this today to compare what I had in my main.cf to what the defaults were - and for some reason I had uncommented a bunch of things that didn't need to be uncommented (because they were the default setting), resulting in a much larger output from the postconf -n command. I know its not a big deal, but any chance of implementing this for dovecot? This would make it easy to keep the conf file (and the -n output) clean and neat. Many, many thanks for 1.0.0! -- Best regards, Charles
On Tue, 2007-05-08 at 16:56 -0400, Charles Marcus wrote:> Hi Timo, > > You were good enough to add the -n flag to the dovecot command to output > the current *changed* config parameters (changed as compared to the > defaults) of the running dovecot process. This makes it much easier to > troubleshoot issues - thanks! > > Another flag that postfix has is the -d flag (postconf -d). This one > outputs all of the DEFAULTS of the current running postfix process/version. > > I just used this today to compare what I had in my main.cf to what the > defaults were - and for some reason I had uncommented a bunch of things > that didn't need to be uncommented (because they were the default > setting), resulting in a much larger output from the postconf -n command. > > I know its not a big deal, but any chance of implementing this for > dovecot? This would make it easy to keep the conf file (and the -n > output) clean and neat.Dovecot's -n actually works a bit differently. It lists only the settings that aren't the same as defaults, not the settings that have been uncommented in dovecot.conf. dovecot -d would be possible also, but I don't see it as that useful. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070509/0e92ad52/attachment.bin>
> Dovecot's -n actually works a bit differently. It lists only the > settings that aren't the same as defaults, not the settings that have > been uncommented in dovecot.conf. dovecot -d would be possible also, but > I don't see it as that useful.Heh - I actually deleted a final comment something like 'or, maybe you could just make -n output based on actual diff from the known default settings for that version vs the current settings, not based on just the uncommented settings in the file' (the wording was awkward), so, you did it right from the beginning... Thanks! Also - did you see my earlier suggestion for adding to the output of -n? Sent on 4/26: I'm the one who suggested the '-n' option to capture the actual config settings that the running dovecot process was using (ala postfix), and you implemented it very quickly - so thanks for that! Now, I'd like to suggest an enhancement... Many people still do not provide basic things like dovecot version, and there are secondary config files like dovecot-ldap, whose settings are not included in the dovecot -n output. How difficult would it be to add these to the output so that the output would include the running dovecot version, as well as any extra config settings from any other files that are loaded when dovecot starts? It would sure make it easier, both for us troubleshooting on our own, and when asking for help on the list. Many thanks, and terrific job on 1.0! Now all dovecot lacks is full support for IMAP ACLs/shared folders, and support for single-instance storage, and it will have no real competition... -- Best regards, Charles