[Dovecot] clarify 'type', 'executable' & 'path' in 2.0 master.conf?

[Timo Sirainen]

On Oct 10, 2009, at 3:57 PM, PGNet Dev wrote:

> @2.0's master.conf, there's, e.g.,
>
> service config {
>  type= config
>  executable =config
>  unix_listener {
>   path = config
>   mode = 0666
>  }
> }
>
> can someone please explain function/usage for the 'type', 'executable'
> & 'path' fields?

There are a few internal special-case services and type specifies what  
type it is. So with type=config Dovecot knows that to reload  
configuration it needs to connect to that service.

executable is the binary name, relative to PKG_LIBEXECDIR. path inside  
unix_listener is the path to the unix socket where to listen for  
connections, relative to base_dir.

> and, for any file paths, are the presumed to be _relative_ to the
> dovecot executable? in $PATH? can they accept full/absolute paths?

They don't use $PATH. Absolute paths are fine.