There were more jobs, and I killed them (not showing that, for brevity, but they were all jobs that I grepped out with `ps aux | grep blkls' just like below):
[code]
g5n ~ # kill 31041 31042 31045 31046
[/code]
This one pair (or whatever to call it) remaining:
[code]
g5n ~ # ps aux | grep blkls
root      4169  0.0  0.0  16800   472 pts/1    S    May07   0:00 sh -c '/usr/bin/blkls' -e -f ext -o 0 -i raw '/Cmn/autopsy/g5nCmn/g5n/images/vgn-Cmn' | '/usr/bin/srch_strings' -a -t d | '/bin/grep'  'Z1_F0331_Zoom_Lovrić_Škaričić\.avi'
root      4170  3.9  0.0  29908   680 pts/1    S    May07 148:01 /usr/bin/blkls -e -f ext -o 0 -i raw /Cmn/autopsy/g5nCmn/g5n/images/vgn-Cmn
root     31473  0.0  0.0  11588  2024 pts/9    S+   21:01   0:00 grep --colour=auto blkls
g5n ~ #
[/code]
An I decide to kill it:
[code]
g5n ~ # kill 4170 4169
g5n ~ # 
[/code]
And I want to make sure it is now dead, but...
...But:
[code]
g5n ~ # ps aux | grep blkls
root     31479  0.0  0.0  16800  2748 pts/1    S    21:05   0:00 sh -c '/usr/bin/blkls' -e -f ext -o 0 -i raw '/Cmn/autopsy/g5nCmn/g5n/images/vgn-Cmn' | '/usr/bin/srch_strings' -a -t d -e l | '/bin/grep'  'Z1_F0331_Zoom_Lovrić_Škaričić\.avi'
root     31480 22.2  0.0  29908  3276 pts/1    S    21:05   0:02 /usr/bin/blkls -e -f ext -o 0 -i raw /Cmn/autopsy/g5nCmn/g5n/images/vgn-Cmn
root     31484  0.0  0.0  11580  2020 pts/9    S+   21:05   0:00 grep --colour=auto blkls
g5n ~ # 
[/code]
I couldn't believe, but look, repeating the same kill line as before shows it's not those processes!
[code]
g5n ~ # kill 4170 4169
bash: kill: (4170) - No such process
bash: kill: (4169) - No such process
g5n ~ # 
[/code]
These really have just been spawned. I didn't run the date in the terminal, but the time, believe you me, was just the one that the ps piped to grep says these new processes have started, 9 pm of May 9th 2015. With incredulity, I looked it up again:
[code]
g5n ~ # ps aux | grep blkls
root     31479  0.0  0.0  16800  2748 pts/1    S    21:05   0:00 sh -c '/usr/bin/blkls' -e -f ext -o 0 -i raw '/Cmn/autopsy/g5nCmn/g5n/images/vgn-Cmn' | '/usr/bin/srch_strings' -a -t d -e l | '/bin/grep'  'Z1_F0331_Zoom_Lovrić_Škaričić\.avi'
root     31480 23.5  0.0  29908  3276 pts/1    S    21:05   0:06 /usr/bin/blkls -e -f ext -o 0 -i raw /Cmn/autopsy/g5nCmn/g5n/images/vgn-Cmn
root     31487  0.0  0.0  11584  2008 pts/9    S+   21:06   0:00 grep --colour=auto blkls
g5n ~ # 
[/code]
And, I can't prove it, but links -g wasn't running on the "http://g5n:9999/31564462051203138502/autopsy" that Autopsy gave me when I started it.
So:
[code]
g5n ~ # kill 31479 31480
g5n ~ # 
g5n ~ # ps aux | grep blkls
root     31489  0.0  0.0  11584  2012 pts/9    R+   21:06   0:00 grep --colour=auto blkls
g5n ~ #
[/code]
It is finally over.

And since Autopsy wasn't running when that job was unnecessarily somehow spawned, I guess it may eventually not be down to Autopsy, but to some other reason.