Date: Tue, 29 May 2001 13:19:35 -0500 From: David Banning <sky_tracker@yahoo.com> To: questions@freebsd.org Subject: Bad system call - workaround help needed Message-ID: <20010529131934.A3725@yahoo.com>
next in thread | raw e-mail | index | archive | help
This SCO program I am running allows me to pipe my reports out to any program. I have to compile it into the database code, which is not open. I am piping to a printer but the program crashes. It works fine if I just pipe it to a shell script like this one; cat $1 > ~/printfile Then I can go "cat ~/printfile | lp -dlj -s" and it prints fine. But for some strange reason, if I expand the program to cat $1 > ~/printfile cat ~/printfile | lp -dlj -s the program crashes, with bad system call - signal 12 If I try and pipe it directly to the print it crashes also. It doesn't _always_ crash either. The only work around I can think of, it running a cron that is looking for files to print every 5 seconds. I've tried a number of nohups and background type & which doesn't seem to help. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010529131934.A3725>