Hi,
On Montag 01 Mai 2006 13:35, Michael Nausch wrote:
Griasdebou!
O.K. I'm back from hospital an will play and search, what happens ...
Am Montag, 1. Mai 2006 07:53 schrieb Jörg Wendel:
please can you check if the file "/video/Clips/Tito_&_Tarantula_-_After_Dark/2005-02-04.22.50.99.99.rec/pr ot ection.fsk" was created by the script.
No, there's no protection.fsk in the subdirectory.
Does you have changed the script "/usr/bin/fskprotect.sh" to the new one?
Jepp, I've made some symlinks to use the right new scripts: tecvdr:/usr/bin # ls -al fs* lrwxrwxrwx 1 root root 43 Apr 30 22:54 fskcheck -> /usr/local/src/VDR/PLUGINS/src/pin/fskcheck lrwxrwxrwx 1 root root 59 Apr 30 22:53 fskcheck-demo.sh -> /usr/local/src/VDR/PLUGINS/src/pin/scripts/fskcheck-demo.sh lrwxrwxrwx 1 root root 56 Apr 30 22:53 fskprotect.sh -> /usr/local/src/VDR/PLUGINS/src/pin/scripts/fskprotect.sh
fsprotect.sh contains: tecvdr:/usr/bin # cat fskprotect.sh
the links and the script looks good, i think the script exits cause it can't check the protection state of the pin plugin. And the reason for this should be the 'permision denied' problem.
ecvdr:/usr/bin # ipcs -q
------ Message Queues -------- key msqid owner perms used-bytes messages 0xd8000000 0 vdr 0 0 0
Ok, thats it, the perms are 0. Sorry it's my bug, i'am using linvdr where vdr is always running as root. For the root user the perms don't matter.
Pleas apply the attached patch to the plugin. BEFORE starting vdr again make sure no system message queue with the wrong permissions is left. Attention only message queues which key starts with 0xd80000?? are from the pin plugin. Don't delete others of your system ;)
Example:
- first list it: linvdr:/etc/vdr# ipcs -q | grep 0xd80000 0xd8000000 393216 root 666 0 0
- now delete it using the listed key(s) (second column) linvdr:/etc/vdr# ipcrm msg 393216
Greetings Jörg