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.000223
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 »

kokoko3k commented on 2015-12-02 11:15

Ops, you're right; i've just updated the PKGBUILD.

nmaggioni commented on 2015-12-02 07:43

/usr/share/gopreload/README comes out as a symlink to itself...?

kokoko3k commented on 2015-05-04 10:46

Did it
https://github.com/kokoko3k/gopreload/commit/cbc1b494b6259fdf2f7976f244bf984b7e0d2265

Einhard commented on 2015-05-02 20:23

Yes, with those changes it works as intended. It was nice try with -HUP as in theory it should make mapandlock hang up, reload config and start again but it seems there are many cases when this just doesn't work.

kokoko3k commented on 2015-05-02 18:57

You're right Einhard, as mapandlock does not react to HUP, the correct way should be:
---------
else
#echo "Nothing changed, Sleeping $LONG_DELAY sec."
sleep $LONG_DELAY
killall mapandlock.$ARCH >/dev/null 2>/dev/null
$INSTALLDIR/bin/mapandlock.$ARCH /tmp/listpreload.txt &
fi
--------
Does it work that way?

I'll fix in the git by monday if is all right.

kokoko3k commented on 2015-05-02 18:57

You're right Einhard, as mapandlock does not react to HUP, the correct way should be:
---------
else
#echo "Nothing changed, Sleeping $LONG_DELAY sec."
sleep $LONG_DELAY
killall -HUP mapandlock.$ARCH >/dev/null 2>/dev/null
$INSTALLDIR/bin/mapandlock.$ARCH /tmp/listpreload.txt &
fi
--------
Does it work that way?

I'll fix in the git by monday if is all right.

Einhard commented on 2015-05-02 16:29

For me it kills mapandlock after LONG_DELAY and doesn't restart it if nothing changed. Culprit is line 83 in StartPreload.sh, 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 so nothing is locked in memory and whole purpose of gopreload is gone. 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:28

For me it kills mapandlock after LONG_DELAY and doesn't restart it if nothing changed. Culprit is line 83 in StartPreload.sh, 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 so nothing is locked in memory and whole purpose of gopreload is gone. 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 after 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:24

For me it kills mapandlock after LONG_DELAY and doesn't restart it if nothing changed. Culprit is line 83 in StartPreload.sh, 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 so nothing is locked in memory and whole purpose of gopreload is gone. 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:23

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 so nothing is locked in memory and whole purpose of gopreload is gone. 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))