[This does _not_ belong on hackers, follow-ups set to questions]
-On [20000206 04:00], Alex ([EMAIL PROTECTED]) wrote:
>
>When I run my script,sometimes I receive next
>message:
>
>"/usr/sbin/wanrouter: line 5 288 Broken pipe
>ls $ROUTER_LOCK_DIR/ 289 Exit 1 | grep -q
>wanpipe*"
Ehm, the above looks kinda weird and would most certainly explain the
broken pipe. A broken pipe is when stdout had a connection to the
stdin of the next program but the pipe got severed somehow (or never got
set up in the first place).
>I use bash-2.03 shell.
>The line is cause to this message is :
>
>ls $ROUTER_LOCK_DIR/ | grep -q wanpipe* && rm
>$ROUTER_LOCK_DIR/*
And this does work from the command line? It looks ok to me.
--
Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/B-rated Coder BSD: Technical excellence at its best
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
There is no greater sorrow than to recall, in misery, the time when we
were happy...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
