Bug#795186: portsentry is starting too early

2019-11-10 Thread Winston Sorfleet
On Tue, 2 Jan 2018 09:46:09 -0700 TheSin wrote: > This bug is really old and really annoying, is there any plans at all on fixing portsentry to start later? > > Currently snmp has a race condition and will start after portsentry 50% of the time, cyrus and dovecot also have a race condition and

Bug#795186: portsentry is starting too early

2018-01-02 Thread TheSin
This bug is really old and really annoying, is there any plans at all on fixing portsentry to start later? Currently snmp has a race condition and will start after portsentry 50% of the time, cyrus and dovecot also have a race condition and start after it some of the time. Obviously this is

Bug#795186: portsentry is starting too early

2016-05-30 Thread TheSin
I am running into the same issue, though for me it’s when I’m in systemd mode. It’s find in sysv. Maybe portsentry should have a proper systemd service file?

Bug#795186: portsentry is starting too early

2015-08-11 Thread Christoph Pleger
Package: portsentry Version: 1.2-13 Hello, In Debian jessie, portsenty is starting too early, that is, it is starting before other services are started that want to use the same ports, therefore blocking these ports so that starting these other services fails. For example, the default