[Bug 932163] New: FETCHMAIL_POLLING_INTERVAL not honoured
http://bugzilla.opensuse.org/show_bug.cgi?id=932163 Bug ID: 932163 Summary: FETCHMAIL_POLLING_INTERVAL not honoured Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: suse_forum@roocomputing.co.uk QA Contact: jsrain@suse.com Found By: --- Blocker: --- I am using openSUSE Tumbleweed on a reasonably fresh install. I configured "mail server" through YaST2 and selected to use fetchmail as a daemon. On completion I checked the running services and I see the following: ps -ef | grep fetch fetchma+ 980 1 0 22:15 ? 00:00:00 /usr/bin/fetchmail -d 900 -f /etc/fetchmailrc In other words the interval is set to 900. However in the "/etc/sysconfig" YaST2 option, the interval is set to 600: cat /etc/sysconfig/fetchmail | grep -v "#" FETCHMAIL_POLLING_INTERVAL="600" FETCHMAIL_FETCHALL="yes" FETCHMAIL_SILENT="no" FETCHMAIL_USER="fetchmail" FETCHMAIL_EXPERT_OPTIONS="" FETCHMAIL_RC_PATH="/etc/fetchmailrc" Unfortunately I could not work out where the fetchmail command was being constructed so I cannot help with a solution. However, it could be possible to specify the interval and the daemon option in the /etc/fetchmailrc file as the following entry: set daemon 600 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=932163 --- Comment #1 from Andrew Beames <suse_forum@roocomputing.co.uk> --- *** Bug 932164 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=932163 Marcel Pennewiß <opensuse@pennewiss.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse@pennewiss.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=932163 http://bugzilla.opensuse.org/show_bug.cgi?id=932163#c2 --- Comment #2 from Marcel Pennewiß <opensuse@pennewiss.de> --- I can confirm this annoying issue. Workaround: Create File /etc/systemd/system/fetchmail.service with .include /usr/lib/systemd/system/fetchmail.service [Service] ExecStart= ExecStart=/usr/bin/fetchmail -d 600 -f /etc/fetchmailrc and run "systemctl daemon-reload" afterwards. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=932163 http://bugzilla.opensuse.org/show_bug.cgi?id=932163#c3 Alexander Scheib <alexander@scheib.info> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexander@scheib.info --- Comment #3 from Alexander Scheib <alexander@scheib.info> --- in my opinion the bug is not fixed in opensuse 42.1.Is this right ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=932163 http://bugzilla.opensuse.org/show_bug.cgi?id=932163#c4 --- Comment #4 from Andrew Beames <suse_forum@roocomputing.co.uk> --- I am now using the leap 42.1 repos (rather than tumbleweed) but it is now a heavily customised mail system. I call fetchmail manually, for example. However, I have just checked /etc/sysconfig/fetchmail and the setting is: FETCHMAIL_POLLING_INTERVAL="300" but, if I start the service: /etc/sysconfig % sudo systemctl start fetchmail and then check: /etc/sysconfig % sudo systemctl status fetchmail fetchmail.service - A remote-mail retrieval utility Loaded: loaded (/usr/lib/systemd/system/fetchmail.service; disabled) Active: active (running) since Sat 2016-01-02 20:15:53 GMT; 6s ago Main PID: 18482 (fetchmail) CGroup: /system.slice/fetchmail.service └─18482 /usr/bin/fetchmail -d 900 -f /etc/fetchmailrc you can see that the daemon has still been kicked off with 900. Note that my /etc/fetchmailrc file only has poll statements in it. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com