Difference between revisions of "Talk:OfflineIMAP"

From ArchWiki
Jump to: navigation, search
(reply to a signal related question)
(systemd timer: new section)
 
(5 intermediate revisions by 3 users not shown)
Line 6: Line 6:
  
 
: In that file is stored PID (process ID) of the current running offlineimap process. You can use this number as an argument to kill command, to send signals. Like this:
 
: In that file is stored PID (process ID) of the current running offlineimap process. You can use this number as an argument to kill command, to send signals. Like this:
: {{Codeline|kill -s SIGUSR1 `cat ~/.offlineimap/pid`}}
+
: {{ic|kill -s SIGUSR1 `cat ~/.offlineimap/pid`}}
 
: You can see more details [https://github.com/nicolas33/offlineimap/commit/e1fb9492f84538df698d6a2f1cfa2738929ed040 here], [[User:Nixie|Nixie]] 13:50, 7 February 2011 (EST)
 
: You can see more details [https://github.com/nicolas33/offlineimap/commit/e1fb9492f84538df698d6a2f1cfa2738929ed040 here], [[User:Nixie|Nixie]] 13:50, 7 February 2011 (EST)
 +
 +
== Warnings ==
 +
Before (re)adding more warnings about offlineimaps alleged lack of stability and the potential to cataclysmically delete all your mail, please provide some examples of where this has actually happenend.
 +
I have been using it exclusively for the last 3 years on at least 3 machines and have experienced no issues. I can't find a single forum thread describing any such massive failures and the repeated attempts
 +
to include warnings on this page is starting to look like scaremongering.
 +
 +
[[User:Jasonwryan|Jasonwryan]] ([[User talk:Jasonwryan|talk]]) 03:14, 6 March 2013 (UTC)
 +
 +
== systemd timer ==
 +
 +
The whole part about killing OfflineIMAP in case of freeze should probably be removed, since offlineimap-oneshot.service includes:
 +
TimeoutStopSec=120
 +
It is being killed by default after 120secons. -- [[User:Midov|Midov]] ([[User talk:Midov|talk]]) 21:32, 15 April 2018 (UTC)

Latest revision as of 21:32, 15 April 2018

http://nicolas33.github.com/offlineimap/#signals says

 You can send SIGINT to OfflineIMAP using (~/.offlineimap/pid) to kill it. SIGUSR1 will force an immediate resync of all accounts. This will be ignored for all accounts for which a resync is already in progress.

Can someone please explain how to send a signal to a file?

In that file is stored PID (process ID) of the current running offlineimap process. You can use this number as an argument to kill command, to send signals. Like this:
kill -s SIGUSR1 `cat ~/.offlineimap/pid`
You can see more details here, Nixie 13:50, 7 February 2011 (EST)

Warnings

Before (re)adding more warnings about offlineimaps alleged lack of stability and the potential to cataclysmically delete all your mail, please provide some examples of where this has actually happenend. I have been using it exclusively for the last 3 years on at least 3 machines and have experienced no issues. I can't find a single forum thread describing any such massive failures and the repeated attempts to include warnings on this page is starting to look like scaremongering.

Jasonwryan (talk) 03:14, 6 March 2013 (UTC)

systemd timer

The whole part about killing OfflineIMAP in case of freeze should probably be removed, since offlineimap-oneshot.service includes:

TimeoutStopSec=120

It is being killed by default after 120secons. -- Midov (talk) 21:32, 15 April 2018 (UTC)