Package Details: gopreload-git r49.ebb83fe-2

Git Clone URL: https://aur.archlinux.org/gopreload-git.git (read-only, click to copy)
Package Base: gopreload-git
Description: Preloads files needed for given programs
Upstream URL: http://forums.gentoo.org/viewtopic-t-622085-highlight-preload.html
Licenses: GPL
Conflicts: gopreload
Provides: gopreload
Submitter: kokoko3k
Maintainer: kokoko3k
Last Packager: kokoko3k
Votes: 26
Popularity: 0.000349
First Submitted: 2013-11-25 11:12
Last Updated: 2016-12-15 12:45

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

Einhard commented on 2015-05-02 16:21

For me it kills mapandlock after LONG_DELAY and doesn't restart it if nothing changed. Culprit is line 83, as I see it if /tmp/enabled.prec.txt and /tmp/enabled.txt don't differ your main loop is omitted, it kills mapandlock.$ARCH and that's all, there is no mapandlock restart after it. If nothing changes in enabled.txt StartPreload.sh will only do

killall -HUP mapandlock.$ARCH >/dev/null 2>/dev/null

infinite number of times, once per LONG_DELAY. You either add

$INSTALLDIR/bin/mapandlock.$ARCH /tmp/listpreload.txt 2>/dev/null >/dev/null &

after killing it in line 83 or just delete it (files in memory won't refresh in this case but few files out of sync probably don't justify constant hdd activity after each LONG_DELAY when you can just restart service on demand when you know many files in memory changed (probably only after large system update))

Einhard commented on 2015-05-02 16:18

For me it kills mapandlock after LONG_DELAY and doesn't restart it if nothing changed. Culprit is line 83, as I see it if /tmp/enabled.prec.txt and /tmp/enabled.txt don't differ your main loop is omitted, it kills mapandlock.$ARCH and that's all, there is no mapandlock restart after it. If nothing changes in enabled.txt StartPreload.sh will only do
[code]killall -HUP mapandlock.$ARCH >/dev/null 2>/dev/null[/code]
infinite number of times, once per LONG_DELAY. You either add
[code]$INSTALLDIR/bin/mapandlock.$ARCH /tmp/listpreload.txt 2>/dev/null >/dev/null &[/code]
after killing it in line 83 or just delete it (files in memory won't refresh in this case but few files out of sync probably don't justify constant hdd activity after each LONG_DELAY when you can just restart service on demand when you know many files in memory changed)

kokoko3k commented on 2015-03-17 16:28

Nothing wrong from what i see.

proshot commented on 2015-03-17 14:12

I was wondering, if gopreload-git is working correctly on my system with the following output of systemctl status gopreload.services

● gopreload.service - gopreload: Preloads files needed for given programs.
Loaded: loaded (/usr/lib/systemd/system/gopreload.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2015-03-17 15:00:35 CET; 10min ago
Main PID: 294 (StartPreload.sh)
CGroup: /system.slice/gopreload.service
├─ 294 /bin/bash /usr/share/gopreload/bin/StartPreload.sh
├─13206 /usr/share/gopreload/bin/mapandlock.x86_64 /tmp/listpreload.txt
└─13275 sleep 300

Mar 17 15:01:03 nsaSystem StartPreload.sh[294]: 0/2422 files could not be preloaded because they were not found (telegram.1000.openf...MB.txt)
Mar 17 15:01:03 nsaSystem StartPreload.sh[294]: 0/95 files could not be preloaded because they were not found (thunar.1000.openfiles-22MB.txt)
Mar 17 15:01:03 nsaSystem StartPreload.sh[294]: 1/4 - Computing preload list...
Mar 17 15:01:03 nsaSystem StartPreload.sh[294]: 2/4 - Computing total MB... skipped
Mar 17 15:01:04 nsaSystem StartPreload.sh[294]: 3/4 - Starting preload cycle at Tue Mar 17 15:01:04 CET 2015
Mar 17 15:01:04 nsaSystem StartPreload.sh[294]: 4/4 - Sleeping 300 sec.
Mar 17 15:06:04 nsaSystem StartPreload.sh[294]: 2/4 - Computing total MB... skipped
Mar 17 15:06:04 nsaSystem StartPreload.sh[294]: 3/4 - Starting preload cycle at Tue Mar 17 15:06:04 CET 2015
Mar 17 15:06:04 nsaSystem StartPreload.sh[294]: 4/4 - Sleeping 300 sec.
Mar 17 15:11:04 nsaSystem StartPreload.sh[294]: /usr/share/gopreload/bin/StartPreload.sh: line 86: 6681 Hangup $IN...ev/null
Hint: Some lines were ellipsized, use -l to show in full.

It seems not to work correctly.

Any idea's?

promike commented on 2015-01-30 15:09

Thank you very much for your help.
I updated my incomplete list with your values.
I don't say I feel any difference, but we did our best.

Thanks again

kokoko3k commented on 2015-01-30 11:12

here my list stripped from unuseful files:
http://pastebin.com/s0MPfH07

kokoko3k commented on 2015-01-30 11:11

did you tried:
gopreload-prepare chromium --user-data-dir
?

here my list stripped from unuseful files:
http://pastebin.com/s0MPfH07

promike commented on 2015-01-30 08:35

Thank you for your quick help!

I've tried what you had advised. You know if I just type simply sudo gopreload-prepare chromium I get:

Chromium can not be run as root.

Please start Chromium as a normal user. To run as root, you must specify an alternate --user-data-dir for storage of profile information.

and I only have an OK button.
I tried what you had said :
sudo gopreload-prepare chromium --user-data-dir=/home/user/.config/chromium

Well unfortunately nothing happened/opened, again... or maybe yes. Next time when I tried to start the chromium it said:

Your preferences can not be read.
Some features may be unavailable and changes to preferences won't be saved.

And it has forgotten all my settings. I tried to remove the default folder under the .config folder, but the message still appeared. I had to remove the whole chromium folder. -Not a big deal, I don't have too much settings-

I don't really know how gopreload works, but if it works for you with chromium can't you just send me your chromium file from the /usr/share/gopreload/enabled folder?

Thanks a lot!

kokoko3k commented on 2015-01-29 14:51

I don't know why chromium does not get "prepared" as a regular user, strace fails in that.
you can use this trick to prepare chromium as root:
gopreload-prepare chromium --user-data-dir

kokoko3k commented on 2015-01-29 14:51

I don't know why chromium does not get preloaded as a regular user, strace fails in that.
you can use this trick to prepare chromium as root:
gopreload-prepare chromium --user-data-dir