When im doing the back up I get a message that a printer went down the reason i get this message is because people dont know how to fill the paper bin,
Well this locks up the terminal and my backup doesnt run.
I need to move the messages to another terminal.
Look in /etc/syslog.conf for any printer error logging, there should be an entry stating to send printer error logging to /dev/console, just remove the /dev/console and restart the syslog daemon. d3funct
zimmer.jon@cfwy.com
The software required `Windows 95 or better', so I installed Linux.
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
So you set your terminal to vt100 emulation and exported it... (must be vt100)
and as root from the command line you entered:?
/usr/sbin/lsvirprt
And it prompted you for the printer and you typed it in....
then it displayed...
To LIST attributes, enter AttributeName1 ... (* for all attributes)
To CHANGE an attribute value, enter AttributeName=NewValue
To FORMAT and EDIT an attribute value, enter AttributeName~v
To EDIT the attribute file, enter ~v
To terminate, press Enter:
and you typed _A=0 (zero)
then you typed si=nobody or si=root
----------
and when you are done you just press enter ?
and it did not work? It should have?
It seems to work for me? Not sure why it did not for you.
For example, si= specifies that the user who submitted the print job should receive the messages, si=mary specifies the user mary should receive the messages, and si=,jim@server02 specifies that both the user who submitted the print job and jim at node server02 should receive intervention messages.
This what I have on a R50 with 30 printers on it samba and other things that throw there error messages to /dev/console.. now all go to /tmp/console.log.`date +%m%y%d`
edit file /etc/rc.local
add this line
swcons /tmp/consolelog.`date +%m%d%y`
This will redirect all console messages to this file note it will create a new file new file evertime the system is rebooted. So you should do clean up of old files once a month or when ever you reboot..
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.