Redirecting all Qdaemon messages to tty0 or file

[Guest_imported]

Ok, I've got a problem that even IBM support has had a hard time trying to help me accomplish.

Running AIX 4.3.3 on an RS/6000

All users use login using either of 2 login names. (done for specific software reasons)

BUT, when a print queue goes down Qdaemon sends the message to random pts's. This interrupts the users work cause they can't see the screen through the Qdaemon error message.

How can I go about redirecting all Qdaemon errors to EITHER just the tty0 (which is the only serial terminal) or to a file??

Chapter11, you were great with the last print queue problem, can you fix this???

Thanks All!!!!!
Anthony

 

[DSMARWAY]

This is a long shot , have a read see what you think

Using the syslogd daemon you can decide where to log certain messages that the system may generate by adding relevant entries in the syslog.conf file under /etc
Do man syslogd , tells you what types of messages can be logged i.e. kern (kernel) , user , mail ( mail subsystem), daemon ( the daemon sub systems , i think qdaemon may come under here ) and theres quite a few others


so your syslog.conf maylook like

daemon.info /var/adm/daemon.log
daemon.crit /var/adm/daemon.log

The message priority levels can be emerg , alert,crit,err,warning,notice, info, debug ( see man syslogd) once an entry has been made in syslog.conf file you need to refresh the syslogd daemon ( refresh syslogd )

Then try a test .

 

[aixqueen]

Printer messages

Use lsvirprt to look at the virtual printer. The _A setting
can be used to determine if messages go to the console, or the submitter's
mail. There is another attribute called "user to receive intervention messages"
which I don't recall the attribute name for, but you can set it to "nobody" and
the messages will be sent to /dev/null. lsvirprt;_ A=0
or
lsvirprt; si = nobody
or
lpr.* /dev/null in /etc/syslog.conf; refresh -s syslogd
or
use a tty driver (w/ Xon/Xoff flow ctrl) instead of an lp driver

MESSAGES
A. Backend generated
1) Intervention required (e.g., printer out of paper). Sent to submitter of job.
Controlled by virtual printer _si attribute (users, separated by commas, to get
intervention messages; null string is job submitter), e.g., si=nobody.

2) Backend error messages (e.g., use of invalid flag). Controlled by the virtual
printer _A attribute, e.g.,_ A=0

 

[Guest_imported]

aixqueen - even though these are remote printers the virtual printer attributes will work???

when i tried lsvirprt and chose the printer i want to change i didn't see any _A setting

any ideas??
thanks
anthony

 

[aixqueen]

I didn't realize these were remote printers...

If the printers were configured with remote printers with local filtering when they were set up, I believe the values may be there and changeable. Not 100% sure on this you would have to try to define a printer with local filtering and see if the virtual printer commands work ..

If not ...I believe syslogd is your only choice.


lpr.* /dev/null in /etc/syslog.conf; refresh -s syslogd
------------------------------------
You would have to try it to see if it gave you the virtual printer attributes...

Standard processing - The traditional type of remote printing. The
remote print server can be any host that supports the lpd remote
print protocol. Print files are sent to the server without
modification, with the assumption that any necessary filtering of the
print files will be performed by the server before sending the files
to the printer.

o Standard with NFS access to server print queue attributes - Similar
to standard processing, except that the server's directory of print
attributes is NFS-mounted by this client. The server must be running
AIX Version 4 and have exported the directory
/var/spool/lpd/pio/@local. The target print queue on the server
cannot be a remote print queue to another server. SMIT displays the
default values for print job options when starting print jobs
destined for the server, and most override values for print job
options can be validated immediately when a job is submitted, instead
of having to wait until later when the job is actually printed.

Local filtering before sending to print server - Provides the capability to
filter the print files and add printer initialization commands before
the print job is sent to the server. The server can be any host that
supports the lpd remote print protocol, and it must pass the print
files to the printer without additional filtering. This capability
can be useful when the server is not capable of providing this
function, when a required filter or font is not available on the
server, or when print output must be consistent regardless of which
type of server prints the job. Note that for printers that require
font management by the server, such as the IBM 3812 Pageprinter, the
IBM 3816 Pageprinter, and when downloadable fonts are used with IBM
Proprinters, this capability may not produce the desired results if
there is more than one client machine.

 

[Guest_imported]

I set up my remote printers using standard processing.

I'll give the syslogd edit a choice.

do you think i should use the lpr.* /dev/null

or qdaemon.* /dev/null (not sure if this is even an option)

thanks
anthony

 

[Guest_imported]

I tried the lpr.* /dev/console and lpr.* /dev/tty0
but still got the error messages on the telnet session and not on the tty.
Any other suggestions??
This is my current syslog.conf:

*.debug /tmp/syslog
lpr.* /dev/tty0

The following are the types of messages I am trying to prevent from going to users. Ant is the user that send the print job using the lp -dgen print.test. And both ant and tty0 got the message. I don't want the USER to get the message. Thanks

Message from ant on pdomainr (UNKNOWN) [Fri Jul 26 17:32:50 EDT 2002] ...
Message from queueing system:
/usr/lib/lpd/rembak -T50 -S netex -P LPT1_PASSTHRU -N /usr/lib/lpd/aixshort //pr
int.test <EOT>

Message from ant on pdomainr (UNKNOWN) [Fri Jul 26 17:32:50 EDT 2002] ...
Message from queueing system:

: (FATAL ERROR) 0781-244 Failed receiving acknowledgement.
<EOT>

Message from ant on pdomainr (UNKNOWN) [Fri Jul 26 17:32:50 EDT 2002] ...
Message from queueing system:
<EOT>

Message from root on pdomainr (UNKNOWN) [Fri Jul 26 17:32:50 EDT 2002] ...
Message from queueing system:
0781-088 Queue gennetex went down, job is still queued:
Backend: /usr/lib/lpd/rembak -T50 -S netex -P LPT1_PASSTHRU -N /usr/lib/lpd/aixshort //print.test
Backend Exit Value: EXITFATAL (0100)
Job Submit Time: Jul 26 17:30:39 2002. Current Time: Jul 26 17:32:50 2002
Use local problem reporting procedures.
<EOT>

 

[Guest_imported]

Has this problem been solved ?