On Fri, Jan 26, 2007 at 11:11:45AM +0100, Marco d'Itri wrote:
> On Jan 26, Sven Luther <[EMAIL PROTECTED]> wrote:
> 
> >   1) write a program writing to stdout and dropping the actual error message
> >   somewhere.
> Just add something like this to the top of the affected scripts:
> 
> exec >> /dev/xxx.log 2>&1

It tells me that the pipe was closed by the other side, not very helpful, the
other side being udevd. The idea was to try to find out more about the exact
error, but i guess maybe adding explicit debugging to udevd is the only way
out here.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to