[exim] Re: Unable to start Exim 4.98

Página Principal
Apagar esta mensagem
Responder a esta mensagem
Autor: Odhiambo Washington
Data:  
Para: Exim-Users
CC: Luca Bertoncello
Assunto: [exim] Re: Unable to start Exim 4.98
On Fri, Nov 15, 2024 at 5:11 PM Luca Bertoncello via Exim-users <
exim-users@???> wrote:

> Hi again!
>
> Next problem trying to install Exim 4.98 (compiled from source) on a
> fresh Debian 12...
>
> I always used a start script that started these instances:
>
>     start-stop-daemon --start --pidfile /var/run/exim1.pid --quiet
> --exec $DAEMON -- "-bd"
>     echo "exim runner 1"
>     start-stop-daemon --start --pidfile /var/run/exim2.pid --quiet
> --exec $DAEMON -- "-q 5m"
>     echo "exim runner 2"
>     start-stop-daemon --start --pidfile /var/run/exim3.pid --quiet
> --exec $DAEMON -- "-qff 1h"
>
> Now, it only can start exim -bd...
> For exim -q and exim -qff 1h I always get an error:
>
> root@root2507:/etc/exim# /opt/exim/bin/exim -q 5m
> exim abandoned: unknown, malformed, or incomplete option -q
>
> What am I doing wrong this time?
>
> P.S.: I know, I should write a systemd Unit file for exim...
> I'll do it as soon as I know how to start the new version on Debian 12...
>


A number of times I did manually compile Exim for Debian-based Linux.
I would just overwrite the default Exim with my compiled version after
"holding" it (sudo apt-mark exim4-daemon-heavy).
I would put the files in the same location /etc/exim4/, and start exim4 the
usual way.
So, let's start with the manual compile. As usual we all use a Makefile
<https://lists.my.co.ke/~wash/Makefile.txt> to do it.
Mine will give you a little grief, but not anything you cannot surmount.
And then you'll just use the system Unit file for Exim:
```
root@eu:/opt# systemctl cat exim4
# /run/systemd/generator.late/exim4.service
# Automatically generated by systemd-sysv-generator

[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/exim4
Description=LSB: exim Mail Transport Agent
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=remote-fs.target
After=nss-lookup.target
After=network-online.target
After=time-sync.target
After=postgresql.service
After=mysql.service
After=clamav-daemon.service
After=greylist.service
After=spamassassin.service
Wants=network-online.target

[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
SuccessExitStatus=5 6
ExecStart=/etc/init.d/exim4 start
ExecStop=/etc/init.d/exim4 stop
ExecReload=/etc/init.d/exim4 reload
```

And save yourself a lot of time :)




--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]

--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/