hpoj-devel

Re: [hpoj-devel] ptal-printd txt file

[<pa...@rc...>]

Richard Phillips wrote:
> I want to capture output of ptal-printd (ptal-printd > foo.txt) but 
> foo.txt never contains any content, whether running as root or user.
> 
> Tried variations with cat and lpr but no luck. Not a serious prob - but 
> any solutions appreciated.

Hi, Richard.  What exactly are you trying to do here?  Normally ptal-printd
doesn't display anything on standard output unless an error occurs.  It
just sits around waiting for data to be written to a pipe and then sends it
to the printer.

David

Re: [hpoj-devel] ptal-printd txt file

[Richard <ric...@bt...>]

> Message: 2
> To: hpo...@li... Cc: pa...@rc... Subject: Re: [hpoj-devel] ptal-printd txt file 
> From: pa...@rc... (David Paschal)
> Date: Wed, 27 Dec 2000 14:41:08 -0800
> Reply-To: hpo...@li...  Richard Phillips wrote:
> 
>> I want to capture output of ptal-printd (ptal-printd > foo.txt) but 
>> foo.txt never contains any content, whether running as root or user.
>>  > Tried variations with cat and lpr but no luck. Not a serious prob - but 
>> any solutions appreciated.
> 
>  Hi, Richard.  What exactly are you trying to do here?  Normally ptal-printd
> doesn't display anything on standard output unless an error occurs.  It
> just sits around waiting for data to be written to a pipe and then sends it
> to the printer.
> 
> David

Thought you may have spotted newbieness of request - I simply wanted a 
text file of ptal's syntax, which is obtained by ptal-printd >& foo.txt, 
of course.

Re: [hpoj-devel] ptal-printd txt file

[<pa...@rc...>]

Richard Phillips wrote:
> Thought you may have spotted newbieness of request - I simply wanted a 
> text file of ptal's syntax, which is obtained by ptal-printd >& foo.txt, 
> of course.
Oh -- silly me!  :-)  Actually, I think "ptal-printd >foo.txt &" would be
the more correct syntax.

David

Re: [hpoj-devel] ptal-printd txt file

[<pa...@rc...>]

I wrote:
> Richard Phillips wrote:
> > Thought you may have spotted newbieness of request - I simply wanted a 
> > text file of ptal's syntax, which is obtained by ptal-printd >& foo.txt, 
> > of course.
> Oh -- silly me!  :-)  Actually, I think "ptal-printd >foo.txt &" would be
> the more correct syntax.
Evidently I was still confused when I wrote that!  I had forgotten that I
had changed ptal-printd to send its messages to standard error rather than
standard output, which was what you were getting at.  So the syntax you
suggested above ("ptal-printd >& foo.txt") is correct after all.  Other
commands I tried that also work include "ptal-printd &>foo.txt" and
"ptal-printd 2>foo.txt" (which is what I typically use).  It would only be
necessary to include the final ampersand if you want it to start in the
background, which isn't needed when running ptal-printd with no parameters,
because it exits right away anyway.

Sorry about the misinformation!  :-)

David