many thanks, much appreciated shawn!
On 9/12/16 04:48, Shawn Bakhtiar wrote:
I believe in order for that to be true you need to use do-release-upgrade
https://help.ubuntu.com/lts/serverguide/installing-upgrading.html
Which also handles the migration of the startup scripts etc
(regardless
I believe in order for that to be true you need to use do-release-upgrade
https://help.ubuntu.com/lts/serverguide/installing-upgrading.html
Which also handles the migration of the startup scripts etc (regardless
upgrades like these always tend to leave loose threads).
For now thought I woul
Right, it was upgraded from Ubuntu 14.10
I thought apt-get dist-upgrade + update + upgrade is supposed to migrate
that stuff?
On 8/12/16 06:39, Shawn Bakhtiar wrote:
Good point. Although since ubuntu 16.x systemD is the default init system,
which begs the question, was the system upgraded o
Good point. Although since ubuntu 16.x systemD is the default init system,
which begs the question, was the system upgraded or is this a fresh install?
> On Dec 7, 2016, at 7:59 AM, sha...@shanew.net wrote:
>
> Since you appear to have both kinds of init files (sysV and systemd),
> you may want
Since you appear to have both kinds of init files (sysV and systemd),
you may want to doublecheck which init system is actually running.
I'm pretty sure you can figure it out by running "dpkg -S /sbin/init"
(this tells you which package owns that file). It will probably say
systemd-sysv, in which
Yeah... it's missing the "after" directive in the [unit] section, which would
have systemD wait until the other services (targets) are up. But also as Marc
mentioned not sure why you would use Monit since systemD (for all it's issues)
does monitor daemons and makes sure to spawn them again if th
Am 2016-11-23 04:11, schrieb Michael Heuberger:
I'm running Spamassassin v3.4.1 here on an headless Ubuntu 16.10
server together with Monit (and Postfix of course). Each time server
restarts, Monit says first that the spamd process is not running (no
PID) but in three minutes later it says the o
Thanks Shawn
Here the contents on my server:
michael.heuberger@binarykitchen /l/s/system ❯❯❯ cat spamassassin.service
[Unit]
Description=Perl-based spam filter using text analysis
[Service]
Type=forking
PIDFile=/var/run/spamassassin.pid
EnvironmentFile=-/etc/default/spamassassin
ExecStart=/usr/
Thanks for that David.
Had a look here:
michael.heuberger@binarykitchen /e/init.d ❯❯❯ head spamassassin
#! /bin/sh
### BEGIN INIT INFO
# Provides: spamassassin
# Required-Start: $remote_fs
# Required-Stop: $remote_fs
# Should-Start: $network $syslog
# Default-Start: 2 3 4 5
# Default-
With Ubuntu 16.10 you should be using systemd.
you can enable dependencies (after directive) which can make sure that all the
services you need are started prior to (in the case of SA) the service you want.
Check your systemD service configuration file:
/usr/lib/systemd/system/spamassassin.servi
I recently set up an email server on Ubuntu 14.10 and kept being
frustrated that on boot various filter software and related milters
were regularly starting after sendmail, sometimes by as much as five
minutes. We don't reboot that server very often, so it took a while
to test various fixes, but
Hi David
I dont know. Not sure how I can find this out whether it does some
DNS/network stuff.
In my other response to John you can see that it takes about 5.69 sec to
start spamassassin.
And no idea how to configure a SA startup dependency on the network
being up. And shouldn't that come
Thanks John for the commands. Here the results
michael.heuberger@binarykitchen /v/log ❯❯❯ sudo time
/etc/init.d/spamassassin start ⏎
Starting spamassassin (via systemctl): spamassassin.service.
0.00user 0.00system 0:05.69elapsed 0%CPU (0avgtext+0avgdata
4904maxresident)k
0inputs+0outputs (0ma
On Tue, 6 Dec 2016, Michael Heuberger wrote:
Thanks John
What commands would you use for shutting down SA properly and to time-measure
its restart procedure?
Hrm. Based on the start/stop commands in what you pasted earlier:
/etc/init.d/spamassassin stop
time /etc/init.d/spam
Thanks John
What commands would you use for shutting down SA properly and to
time-measure its restart procedure?
- Michael
On 6/12/16 11:15, John Hardin wrote:
On Tue, 6 Dec 2016, Michael Heuberger wrote:
Anyone?
If you shut down SA and run the /etc/init.d/spamassassin script to
restar
On Tue, 6 Dec 2016, Michael Heuberger wrote:
Anyone?
On 23/11/16 16:11, Michael Heuberger wrote:
Hello folks
New here :)
I'm running Spamassassin v3.4.1 here on an headless Ubuntu 16.10 server
together with Monit (and Postfix of course). Each time server restarts,
Monit says first that th
On Tue, 6 Dec 2016, Michael Heuberger wrote:
Anyone?
If you shut down SA and run the /etc/init.d/spamassassin script to restart
it, how long does that take to complete?
Is there something like a rules recompile built into that?
On 23/11/16 16:11, Michael Heuberger wrote:
Hello folks
Anyone?
On 23/11/16 16:11, Michael Heuberger wrote:
Hello folks
New here :)
I'm running Spamassassin v3.4.1 here on an headless Ubuntu 16.10
server together with Monit (and Postfix of course). Each time server
restarts, Monit says first that the spamd process is not running (no
PID) but in
Hello folks
New here :)
I'm running Spamassassin v3.4.1 here on an headless Ubuntu 16.10 server
together with Monit (and Postfix of course). Each time server restarts,
Monit says first that the spamd process is not running (no PID) but in
three minutes later it says the opposite, that it is b
19 matches
Mail list logo
