I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used
/etc/dovecot from current Centos 6 Dovecot 2.1
I can start/stop Dovecot with dovecot / doveadm stop
BUT when I tried 'systemctl' I get
# systemctl status dovecot
? dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled;
vendor preset: disabled)
Active: inactive (dead)
Docs: man:dovecot(1)
http://wiki2.dovecot.org/
how do I fix this, or, do I need to fix it ?
or maybe I need to pursue this on ghettoforge list
> On December 16, 2017 at 1:59 AM voytek at sbt.net.au wrote: > > > I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used > /etc/dovecot from current Centos 6 Dovecot 2.1 > > I can start/stop Dovecot with dovecot / doveadm stop > > BUT when I tried 'systemctl' I get > > # systemctl status dovecot > ? dovecot.service - Dovecot IMAP/POP3 email server > Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled; > vendor preset: disabled) > Active: inactive (dead) > Docs: man:dovecot(1) > http://wiki2.dovecot.org/ > > how do I fix this, or, do I need to fix it ? > > or maybe I need to pursue this on ghettoforge list >Try systemctl enable dovecot Aki
On 16/12/17 20:45, Aki Tuomi wrote:>> I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used >> /etc/dovecot from current Centos 6 Dovecot 2.1 >> >> I can start/stop Dovecot with dovecot / doveadm stop >> >> BUT when I tried 'systemctl' I get >> >> # systemctl status dovecot >> ? dovecot.service - Dovecot IMAP/POP3 email server >> Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled; >> vendor preset: disabled) >> Active: inactive (dead) >> Docs: man:dovecot(1) >> http://wiki2.dovecot.org/ >> >> how do I fix this, or, do I need to fix it ? >> >> or maybe I need to pursue this on ghettoforge list >> > > Try systemctl enable dovecot...and systemctl start dovecot. You need to be starting and stopping dovecot with systemctl (or the older service command which still works in CentOS 7), if you do not then systemd cannot track the running state properly. Peter