Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How do i stop messages from coming across the command console

Status
Not open for further replies.

call

Technical User
Joined
Oct 31, 2000
Messages
127
Location
US
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.

 
Thank you, I would like to know if i can direct it to a file instead of deleting it out.

something like this

/home/don

 
Of course... simply change [tt]/dev/console[/tt] to [tt]/path/to/file[/tt].
I hope it works...
Unix was made by and for smart people.
 
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


 
Thank you but nothing is working.

the _A=0 doesnt work the Attribute is not there

I have change it to a file and still comming across the screen.

i have change it to /dev/tty1 and its still comming across the sreen.

I didnt delete it yet Im trying not to.

here is what the last 3 lines in the file said.

# mail.debug /usr/spool/mqueu/syslog
# *.debug /dev/console I change it to /dev/tty1
# *.crit *

what do you think
 
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.

A stderr returned? 0:no; 1:yes, & pipelines; 1
2:yes, & values, pipelines
 
Use the command swcons command to swap output to the console to a file.

swcons /tmp/console.log

A job can be set up to rollover the log files.
 
thanks i will try it.

Aixqueen I tryed it again and nothing the problem is the way the printer is setup
It doesnt have the _A Attribute
 
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..

Hope this is what you are wanting..

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top