I, for one, won't be removing anymore spam unless at least some form of action is taken.
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
05 08/24/07 8:06:07.701 Creating child 63 <0xb795f6d0>Not sure what it exactly means, but I don't like the sound of it.
05 08/24/07 8:06:07.701 Note: Device manager has attached a device of type 43 that this has no custom event handler for. It will not fire events. <0xb795f6d0>
05 08/24/07 8:06:07.701 Note: Device manager has attached a device of type 43 that this has no custom handler for. This is normal for IR. <0xb795f6d0>
05 08/24/07 8:06:09.636 statechange Reply: Sorry, after all that searching, I can't determine which child device should be sent the pin_changed <0xb615bb90>
# /etc/default/vdrIf only I had a clue what would need changing, supposing that indeed that is the problem (the /usr/share/doc/README.Debian does not exist, not that I would expect it to contain anything useful anyway).
# See also /usr/share/doc/README.Debian
# Change to 1 to enable vdr's init-script
# Change this to 1 if you want vdr to be able to shutdown the
# Options that will be passed to vdr's commandline
# for example: OPTIONS="-w 15"
+ /usr/pluto/bin/Spawn_Wrapper.sh ./VDR -d 58 -r 127.0.0.1 -l /var/log/pluto/58_VDR.log
Visit www.plutohome.com for source code and license information