by Joanna Li » Thu, 23 Dec 1999 04:00:00
by Greg Andre » Thu, 23 Dec 1999 04:00:00
Ask the admin to shut that machine down for a few minutes while
you're on the phone with him/her. You'll see the messages stop.
When that machine boots back up, you'll see the messages resume.
Then you can make that machine's admin really find the problem
and stop it.
-Greg
--
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
by John Riddoc » Fri, 24 Dec 1999 04:00:00
--
http://www.scms.rgu.ac.uk/staff/jr/
First Law of Socio-Genetics:
Celibacy is not hereditary.
by Joanna Li » Fri, 24 Dec 1999 04:00:00
There were tons of files(symbolic links) under /var/spool/print and they
pointed to the files that were not exist. The removal of those links certainly
stopped the message.
I think what happened was somebody tried to sent the print job and noticed the
printer wasn't there. They didn't cancel the job and resubmit a new job to the
right printer and got it done. Then they removed the files they wanted to
print before the timeout of the bad print job. Those links had the root as
owner and the group id was the same as the pointing directory.
One thing I don't know is how to prevent this from happening from the server
side. That printer wasn't even defined on the client box.
Thanks again for all your help. Finally the annoying message stopped.
Happy holiday.
Joanna
> >>Dec 22 16:28:11 todd bsd-gw[1543]: request to
> >>bsttbwel_user_proc_grant.sql.ps (unknown printer) from dledq.itg.ti.com
> > Nevertheless, it's making connections to TCP port 515 on your machine
> > and asking to send a print job to a printer that is unknown to your
> > machine.
> > Ask the admin to shut that machine down for a few minutes while
> > you're on the phone with him/her. You'll see the messages stop.
> > When that machine boots back up, you'll see the messages resume.
> > Then you can make that machine's admin really find the problem
> > and stop it.
> Ask him/her to check /var/spool/print; we had a machine do a similar thing
> a while back and it was actually printd causing the problem. Emptying the
> directory cleared the problem. Also make damn sure that the printer has
> been removed from the client box.
> --
> http://www.scms.rgu.ac.uk/staff/jr/
> First Law of Socio-Genetics:
> Celibacy is not hereditary.
by Dryas » Fri, 14 Jan 2000 04:00:00
someting is using the print utility
start the truss cmd on the lpsched daemon and the syslogd daemon
exa truss -p "PID of the daemon" -t open,read,write
It is possible this is comming from a remote system (old delted queue on the
server)
start the snoop cmd
nslookup dledq.itg.ti.com =>to get ip addr
snoop -v "ip addre of that system"
regards ds wim de preter
____________________________________________________
1. trimming /var/adm/messages & /var/adm/syslog
Is there any program out there that will help keep my messages & syslog
files at a reasonable size? I was thinking about writing a shell script
to remove any lines from more than five days ago, but I thought I would
ask if something was available before going through the trouble.
Thanks.
2. FTP on Solaris 7 in GUI mode
3. Clean way to remove /var/adm/messages and /var/adm/syslog
5. bootp messages in /var/adm/messages, disable?
6. Network pbs
7. U5/333, Sol 7: weird messages in /var/adm/messages
8. redhat 9.0 and networkeverywhere nc100u-wm PCI network card
9. Message source in /var/adm/messages
10. "setuid fail" message in /var/adm/messages
11. syslogd failed to log message to /var/adm/messages
12. Innd leaving messages in /var/adm/messages & fun with a serial port
13. Messages in /var/adm/messages