|
Bugzilla – Full Text Bug Listing |
| Summary: | FETCHMAIL_POLLING_INTERVAL not honoured | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Andrew Beames <suse_forum> |
| Component: | YaST2 | Assignee: | Peter Varkoly <varkoly> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_6EwEDK7-dH, forgotten_GJ25OdPlc3 |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andrew Beames
2015-05-24 22:22:58 UTC
*** Bug 932164 has been marked as a duplicate of this bug. *** 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. in my opinion the bug is not fixed in opensuse 42.1.Is this right ? 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.
Duplicated *** This bug has been marked as a duplicate of bug 905673 *** |