From: Matthias A. <mat...@gm...> - 2022-05-31 21:43:24
|
Am 31.05.22 um 19:17 schrieb Mauro Folcarelli: > > Thank you Matthias. > > I removed the "--daemon" from the command line and replaced it with > --nodetach > > The result is the same: > > mag 31 19:09:18 mfhost fetchmail[4255]: fetchmail: POP3> QUIT > mag 31 19:09:18 mfhost fetchmail[4255]: fetchmail: POP3< +OK Logging out. > mag 31 19:09:18 mfhost fetchmail[4255]: fetchmail: 6.4.30 > interrogazione di pop.tiscali.it (protocollo POP3) su mar 31 mag 2022, > 19:09:18: completata > mag 31 19:09:18 mfhost fetchmail[4255]: fetchmail: interruzione > normale, stato 1 > mag 31 19:09:18 mfhost systemd[1327]: fetchmail.service: Main process > exited, code=exited, status=1/FAILURE > ░░ Subject: Uscito processo unità > ░░ Defined-By: systemd > ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > ░░ > ░░ Un processo ExecStart appartenente all'unità UNIT è uscito. > ░░ > ░░ Il codice di uscita del processo è 'exited' ed è uscito con 1. > mag 31 19:09:18 mfhost systemd[1327]: fetchmail.service: Failed with > result 'exit-code'. > ░░ Subject: Unit fallita > ░░ Defined-By: systemd > ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > ░░ > ░░ Unità UNIT entrata nello stato 'failed' (fallito) con risultato > 'exit-code'. > > Fetchmail worked well, but after having downloaded emails from > provider's server, it ended. > > The --nodetach option didn't produced the result I was expecting: > fetchmail remaining "running" and downloading emails every X time. > > If it's not possible to achieve this, ... ok I will use cron and > launch fetchmail every X time. > it's either: --nodetach --daemon 300 or: using cron/systemd timers and no --daemon option (or --daemon 0). |