Just to add to the mix, this is on a NAS which has never been suspended:

    #               Uptime | System                                     Boot up
----------------------------+---------------------------------------------------
->   1   142 days, 12:48:22 | Linux 3.16.0-4-amd64      Tue Jun 13 00:09:42 2017
    2   142 days, 12:35:40 | Linux 3.16.0-4-amd64      Mon Jun 12 23:56:46 2017
    3   122 days, 13:04:07 | Linux 3.16.0-4-amd64      Sun Dec  4 22:20:02 2016
    4    90 days, 18:44:38 | Linux 3.16.0-4-amd64      Thu Jun 16 15:18:37 2016
    5    45 days, 11:05:00 | Linux 3.16.0-4-amd64      Thu Apr 21 22:41:26 2016
    6    41 days, 18:49:54 | Linux 3.16.0-4-amd64      Sat Sep 17 19:38:26 2016
    7    30 days, 04:32:30 | Linux 3.16.0-4-amd64      Thu Nov  3 18:58:36 2016
    8    28 days, 23:15:32 | Linux 3.16.0-4-amd64      Thu Apr  6 15:08:41 2017
    9    27 days, 12:45:43 | Linux 3.16.0-4-amd64      Sat May 13 08:44:48 2017
   10    10 days, 02:14:25 | Linux 3.16.0-4-amd64      Mon Jun  6 09:47:21 2016
----------------------------+---------------------------------------------------
NewRec     0 days, 00:12:41 | since                     Thu Nov  2 11:45:23 2017
   up   698 days, 09:15:40 | since                     Thu Apr 21 22:41:26 2016
 down  -138 days, -18:-59: | since                     Thu Apr 21 22:41:26 2016
  %up              124.802 | since                     Thu Apr 21 22:41:26 2016

This bug is now at least 5 years old and IMHO seems to suggest that the package
simply does not work. Should we consider dropping it?

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄⠀

Reply via email to