[Dovecot] Binary locations
Where do you think the following binaries should be installed to? The possible locations are:
- bin/
- sbin/
- libexec/dovecot/ (or lib/dovecot/ in most Linux distros)
So the binaries are:
- These probably belong to bin/ or sbin/ or both:
- authtest
- dovecotpw
- doveadm
- Binaries that you might want to call from mail_executable setting:
- rawlog
- gdbhelper
- Index file dumping programs, mostly meant for debugging problems:
- idxview
- listview
- logview
- mailboxlogview
- threadview
- Some extra tools that might be useful sometimes:
- imap-utf7 : Encode/decode IMAP mailbox names (mUTF-7 <-> UTF-8)
- maildirlock : Lock a Maildir, primarily intended for compressing files in maildir
And perhaps some of the binaries should be renamed? The authtest actually now looks like a bad name. Maybe it should have been "doveauthtest" or "dovecot-authtest" or ..?
On Tue, 2009-10-06 at 11:32 -0400, Timo Sirainen wrote:
- These probably belong to bin/ or sbin/ or both:
- authtest .. And perhaps some of the binaries should be renamed? The authtest actually now looks like a bad name. Maybe it should have been "doveauthtest" or "dovecot-authtest" or ..?
And if I were forward-looking, maybe dovesasl or dovecot-sasl or dovesasltest or dovecot-sasltest or something. So when in future Dovecot also has SASL client support this could be used to test authentication using all SASL mechanisms.
On 6 Oct 2009, at 16:32, Timo Sirainen wrote:
Where do you think the following binaries should be installed to?
Hi Timo. IMO
<anchor>/sbin is for the dovecot daemon, <anchor>/libexec/dovecot is for supporting tools & utilities <anchor>/lib is for dovecot's (shared) libraries <anchor>/etc is for config files
On Tue, 2009-10-06 at 11:32 -0400, Timo Sirainen wrote:
- These probably belong to bin/ or sbin/ or both:
- doveadm
doveadm is supposed to be this featureful thing that can do all kinds of admin-related stuff. Perhaps one possibility would be to make all of these its subcommands:
- authtest
doveadm auth ..
- dovecotpw
doveadm pw ..
- Index file dumping programs, mostly meant for debugging problems:
- idxview
- listview
- logview
- mailboxlogview
- threadview
doveadm dump <file> (automatically detects what type the file is).
- Some extra tools that might be useful sometimes:
- imap-utf7 : Encode/decode IMAP mailbox names (mUTF-7 <-> UTF-8)
doveadm mutf7 ..
- maildirlock : Lock a Maildir, primarily intended for compressing files in maildir
This could stay separate.
El Martes 06 Octubre 2009 a las 17:57, Timo Sirainen escribió:
doveadm is supposed to be this featureful thing that can do all kinds of admin-related stuff. Perhaps one possibility would be to make all of these its subcommands:
+1
-- Joseba Torre. Vicegerencia de TICs, área de Explotación
On Oct 6, 2009, at 11:57 AM, Timo Sirainen wrote:
On Tue, 2009-10-06 at 11:32 -0400, Timo Sirainen wrote:
- These probably belong to bin/ or sbin/ or both:
- doveadm
doveadm is supposed to be this featureful thing that can do all
kinds of admin-related stuff. Perhaps one possibility would be to make all of these its subcommands:
This is what I ended up doing yesterday.
- authtest
doveadm auth ..
doveadm auth doveadm user
- dovecotpw
doveadm pw ..
Yep.
- Index file dumping programs, mostly meant for debugging problems:
- idxview
- listview
- logview
- mailboxlogview
- threadview
doveadm dump <file> (automatically detects what type the file is).
Yep.
- Some extra tools that might be useful sometimes:
- imap-utf7 : Encode/decode IMAP mailbox names (mUTF-7 <-> UTF-8)
doveadm mutf7 ..
I'm not sure about this. Doesn't seem like it's much of an "admin"
feature. For now it's in libexec/imap-utf7.
- maildirlock : Lock a Maildir, primarily intended for compressing files in maildir
This could stay separate.
Stayed separate.
On 10/06/2009 05:32 PM Timo Sirainen wrote:
Where do you think the following binaries should be installed to? The possible locations are:
- bin/
- sbin/
- libexec/dovecot/ (or lib/dovecot/ in most Linux distros)
So the binaries are:
- These probably belong to bin/ or sbin/ or both:
- authtest
- dovecotpw
- doveadm
- Binaries that you might want to call from mail_executable setting:
- rawlog
- gdbhelper
- Index file dumping programs, mostly meant for debugging problems:
- idxview
- listview
- logview
- mailboxlogview
- threadview
- Some extra tools that might be useful sometimes:
- imap-utf7 : Encode/decode IMAP mailbox names (mUTF-7 <-> UTF-8)
- maildirlock : Lock a Maildir, primarily intended for compressing files in maildir
And perhaps some of the binaries should be renamed? The authtest actually now looks like a bad name. Maybe it should have been "doveauthtest" or "dovecot-authtest" or ..?
under $PREFIX/bin: authtest (or doveauthtest) dovecotpw imap-utf7 maildirlock
under $PREFIX/sbin: doveadm doveconf
under $PREFIX/libexec/dovecot (or $PREFIX/lib/dovecot): rawlog gdbhelper
Hm, all the *view utilities also under $PREFIX/libexec/dovecot
Regards, Pascal
The trapper recommends today: f007ba11.0927917@localdomain.org
On Tuesday 06 of October 2009, Pascal Volk wrote:
On 10/06/2009 05:32 PM Timo Sirainen wrote:
Where do you think the following binaries should be installed to? The possible locations are:
- bin/
- sbin/
- libexec/dovecot/ (or lib/dovecot/ in most Linux distros)
So the binaries are:
- These probably belong to bin/ or sbin/ or both:
- authtest
- dovecotpw
- doveadm
- Binaries that you might want to call from mail_executable setting:
- rawlog
- gdbhelper
- Index file dumping programs, mostly meant for debugging problems:
- idxview
- listview
- logview
- mailboxlogview
- threadview
- Some extra tools that might be useful sometimes:
- imap-utf7 : Encode/decode IMAP mailbox names (mUTF-7 <-> UTF-8)
- maildirlock : Lock a Maildir, primarily intended for compressing files in maildir
And perhaps some of the binaries should be renamed? The authtest actually now looks like a bad name. Maybe it should have been "doveauthtest" or "dovecot-authtest" or ..?
under $PREFIX/bin: authtest (or doveauthtest) dovecotpw imap-utf7 maildirlock
Nooo, these are too generic names to be in bin (also not $PREFIX/bin but @bindir@ as in autoconf convention).
Everything that's not meant to be run by hand should be in @libdir@/dovecot (or @libexecdir@/dovecot).
Proposition of "doveadm subcommand" was much nicer than splitting into tons of bin/sbin utils.
doveadm subcommand can actually simply call @libdir@/dovecot/subcommand if someone want's separate binaries instead of single one.
Regards, Pascal
-- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/
ummm... I like the idea of an anchor as per Jim Redi
<anchor>/sbin is for the dovecot daemon, <anchor>/libexec/dovecot is for supporting tools & utilities <anchor>/lib is for dovecot's (shared) libraries <anchor>/etc is for config files
...I use /usr/local for that in my installation. Which means that, if upgrades (of the OS) do messy things to the contents of /etc/ or/bin or..., the dovecot stuff is in /usr/local/etc, /usr/local/bin or sbin and is left alone. And, of course, the anchor can be null.
Timo Sirainen wrote:
Where do you think the following binaries should be installed to? The possible locations are:
- bin/
- sbin/
- libexec/dovecot/ (or lib/dovecot/ in most Linux distros)
So the binaries are:
- These probably belong to bin/ or sbin/ or both:
- authtest
- dovecotpw
- doveadm
- Binaries that you might want to call from mail_executable setting:
- rawlog
- gdbhelper
- Index file dumping programs, mostly meant for debugging problems:
- idxview
- listview
- logview
- mailboxlogview
- threadview
- Some extra tools that might be useful sometimes:
- imap-utf7 : Encode/decode IMAP mailbox names (mUTF-7 <-> UTF-8)
- maildirlock : Lock a Maildir, primarily intended for compressing files in maildir
And perhaps some of the binaries should be renamed? The authtest actually now looks like a bad name. Maybe it should have been "doveauthtest" or "dovecot-authtest" or ..?
-- "One must think like a hero to behave like a merely decent human being."
- May Sarton Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean@bard.edu voice: 845-758-7475, fax: 845-758-7035
Timo Sirainen wrote:
Where do you think the following binaries should be installed to? The possible locations are:
- bin/
- sbin/
Should these not be /usr/bin and /usr/sbin ?
I believe that /bin and /sbin are for system essentials and /usr/bin for package installed binaries?
- libexec/dovecot/ (or lib/dovecot/ in most Linux distros)
I haven't read the FHS on these, but empirically this seems to be used only for internal system binaries, ie not executed by the user. On my systems /lib/whatever isn't pathed and so you couldn't run them from a command line
I agree that it could be helpful to have a multi-talented admin utility. Additionally don't overlook being able to symlink the binary to some other name and have it execute as this function by name, ie "multicall" a la busybox, etc
Cheers
Ed W
Ed W wrote:
Timo Sirainen wrote:
Where do you think the following binaries should be installed to? The possible locations are:
- bin/
- sbin/
Should these not be /usr/bin and /usr/sbin ?
I believe that /bin and /sbin are for system essentials and /usr/bin for package installed binaries?
Timo did not put a leading / in there - I assume that means add your $PREFIX to those paths.
~Seth
participants (9)
-
Arkadiusz Miskiewicz
-
Charles Marcus
-
Ed W
-
Jim Reid
-
Joseba Torre
-
Pascal Volk
-
Seth Mattinen
-
Stewart Dean
-
Timo Sirainen