Hi all and thanks for replies.
It seems that trackers already runs under ionice (at least on my machine)
.
> 2146 lpouzenc 20 0 465412 15988 8168 S 96,6 0,4 0:05.16
tracker-store
> 2132 lpouzenc 39 19 1104792 19016 11496 R 58,0 0,5 0:05.68
tracker-miner-f
>lpouzenc@lud-GB1:~$ ionice -p 2146 2132
> idle
> idle
I was thinking to suggest using pid file to signal existance of other
"crawlers" instances. For /var/run, Debian FHS says <program-name.pid>,
so may use a generic folder like /var/run/crawlers/ or so. /var/lock is
more apropriate ? Already rwxrwxrwx although.
>
https://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#VARLOCKLOCKFILES
> Lock files for devices and other resources shared by multiple
applications, such as the serial device lock files that were originally
found in either /usr/spool/locks or /usr/spool/uucp, must now be stored
in /var/lock.
There is probably a problem about the ownership of the suggestion
subfolder (which package creates it, which user/group/rights on the folder).
strace suggest that mlocate protect itself from parallel exec by locking
his db file.
> open("/var/lib/mlocate/mlocate.db", O_RDWR) = 4
> read(4, "\0mlocate\0\0\0\370\0\1\0\0/\0prune_bind_mou"..., 8192) = 8192
> fcntl(4, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) =
-1 EAGAIN (Resource temporarily unavailable)
tracker-control opens all /proc/*/cmdline to find his friends ? Sounds
weird.
> lpouzenc@lud-GB1:~$ strace -ff -e lstat tracker-control 2>&1
> Found 210 PIDs…
> Process 3210 attached
> [pid 3209] lstat("/proc/3209/cmdline", {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
> [pid 3209] lstat("/proc/1/cmdline", {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
> [pid 3209] lstat("/proc/2/cmdline", {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
> [pid 3209] lstat("/proc/3/cmdline", {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
> [pid 3209] lstat("/proc/5/cmdline", {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
> [pid 3209] lstat("/proc/7/cmdline", {st_mode=S_IFREG|0444,
st_size=0, ...}) = 0
It seems that updatedb.mlocate and tracker does not use any pid file..
so I may go wrong :)
Why tracker don't use PID's ? It about the "random" user of the spawned
processes ?
Potential troll : Is systemd could solve that ? (I know that tracker is
started via xdg autostart and updatedb via cron)
Regards,
Ludovic
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
