The PostScript you sent works fine for Do_sync; it doesn't work in Do_waitend. I think the issue is that Do_sync() puts a \n after ps_status_code (ifhp.c:3028), while Do_waitend() does not. (Didn't notice that until now...) The extra comment effectively added a newline after the command, and no newline after the comment.
end_status is busy:idle by default; I just added "waiting" (and the versions with semicolons). In my experience, as long as there's an AppleTalk connection, the status will be at least "waiting", sometimes "busy" (if it happens to be in the middle of processing the echo command, for instance). So ifhp can't wait for "idle" by keeping the connection to the printer open and querying status. _Rob At 9:49am, Patrick Powell wrote: > > From [EMAIL PROTECTED] Mon Apr 15 17:21:43 2002 > > Date: Mon, 15 Apr 2002 19:32:24 -0400 > > From: Rob Joyce <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Re: LPRng: Netatalk, LaserWriter, and ^D > > > > Think I've got this pretty much figured out. > > > > First, ps_eoj@ was causing problems because ifhp was looking for messages > > like "%%[ echo: ... ]%%\n", but the printer wasn't putting a newline at > > the end. I gather this is due to the way the ps_status_code string is > > read in from ifhp.conf; adding an extra PostScript comment line at the end > > fixed it (I added "%%EOF" for good measure). > > > > Second, netatalk's pap silently discarded nearly all of the status > > messages. I hacked pap.c to instead put the messages on stderr, > > surrounded by "%%[ " and " ]%%\n" (and throttled the message rate a bit, > > as there were cases when pap was grabbing status _far_ too often). In > > order to work with this modification, ifhp needed the following options: > > ps_eoj@,ps_ctrl_t@,end_status=idle:busy:waiting:busy;:waiting; > > > > I admit this isn't the most elegant of solutions, but it lets AppleTalk > > printing work without having to resort to status@. > > > > _Rob > > What exactly did you do? i.e. 'added "%%EOF"...' sort of makes sense, > but how did you get it to put out a new line? > > By the way, does this work: > > %!PS-Adobe-2.0 > ( %%[ echo: NAME ]%% ) print () = flush > > Note the () = flush seems to do something to cause the \n to be put out. > > Also, > ps_eoj@,ps_ctrl_t@,end_status=idle:busy:waiting:busy;:waiting; > ^^^^^^^^^^^^^^^^^ > idle:busy:waiting ??? > > Patrick Powell > > > ----------------------------------------------------------------------------- > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST > The address you post from MUST be your subscription address > > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests > or lprng-digest-requests) with the word 'help' in the body. For the impatient, > to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] > with: | example: > subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] > unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] > > If you have major problems, send email to [EMAIL PROTECTED] with the word > LPRNGLIST in the SUBJECT line. > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
