Required by (0)

Sources (2)

Latest Comments

Xavion commented on 2017-03-29 22:28

I don't seem to have that problem here. If I kill the process manually, I have no trouble restarting the service. It's worth noting that I have not modified either of the configuration files from their defaults.

ibrokemypie commented on 2017-03-29 08:18

Is there any way to prevent breaking when it does not cleanly quit? Right now it breaks the state file, meaning it will no longer run as a service until it is removed.

Xavion commented on 2016-09-02 22:16

I think you mean that your 'preload' log file is empty. So long as the output of "systemctl status preload.service" looks good, everything should be okay.

KarlFiabeschi commented on 2016-09-01 07:00

xyproto commented on 2014-01-25 12:36

Because of the reasons in my previous comment. Note that while the statistics are interesting, packages are moved only because a TU/Dev wishes to maintain it, not because of popularity.

triplc commented on 2014-01-25 11:40

Why "preload" is moved out of [community]? In popularity statistics ( https://www.archlinux.de/?page=PackageStatistics ), "preload" popularity is 9.62%, ways higher than many other packages in [community]. Well, "preload" is old and not updated, but currently there is no other alternatives for that functionality.

xyproto commented on 2013-07-18 22:05

Moved from [community]. It was an orphan that no other package depended on and of little interest. If a TU or Dev should feel like it, it can easily be moved back to one of the official repos in the future.

xyproto commented on 2013-07-18 22:04

Moved from [community]. It was an orphan that no other package depended on and that nobody seemed interested in adopting. If a TU or Dev feels like it, it can easily be moved back to one of the official repos in the future.