🚀 go-pugleaf

In article <C17xuE.JM2@news.cso.uiuc.edu>, dpape@imlab (Daniel X Pape) writes:
|> I looked at a ps -e listing of the current processes...
|> 
|> and there were at least 25 sendmail processes running.
|> 
|> What could cause sendmail to be run more than once? I thought that
|> the only place that sendmail was invoked was by init on startup.
|> 

Sounds like you have undeliverable mail bouncing somewhere.
Everytime sendmail needs to deliver a messge, it forks off
another process.

|> I've rebooted the machine a few times, and this doesn't seem to help.
|> Killing all but one of the processes doesn't work either.
|> 
|> 

What you should do is:
	1) killall sendmail
	2) cd /usr/spool/mqueue
	3) rm *  <- This assumes that you don't have any mail messages 
                    you want to keep.  If that is not true, you may want
                    to mv all these files somewhere else and look at them.
                    Also, if there are alot of messages, you may have to
                    par off the wildcard by using A*, B* etc.
                    Whatever you do, DO NOT do .* 

|> OH-- also when running osview.... there are alway around 60-70 graphics
|> interrupts every second, and about 250-300 system interrupts a second.
|> EVEN when the machine is just sitting there with only one user!!

I don't have an answer for this.
--
Stephen Chew (chew@csd.sgi.com) "Have a Happy New Year,
SGI Product Support              but please recycle the old one.  
				  	Green earth and all the rest."

In article <C17xuE.JM2@news.cso.uiuc.edu>, dpape@imlab (Daniel X Pape) writes:
|> I looked at a ps -e listing of the current processes...
|> 
|> and there were at least 25 sendmail processes running.
|> 
|> What could cause sendmail to be run more than once? I thought that
|> the only place that sendmail was invoked was by init on startup.
|> 
|> I've rebooted the machine a few times, and this doesn't seem to help.
|> Killing all but one of the processes doesn't work either.
|> 
|> 
|> OH-- also when running osview.... there are alway around 60-70 graphics
|> interrupts every second, and about 250-300 system interrupts a second.
|> EVEN when the machine is just sitting there with only one user!!
|> 
|> 	
|> 	Problems... Problems...
|> 
|> 
|> 
|> Dan Pape


if you have not configured the sendmail program configuration file (/usr/lib/sendmail.cf), you can have runaway sendmail, ie sendmail
continues spawning other sendmails trying to deliver undeliverable 
mail.

if you think this is the case, I suggest the following...

	1) Stop the mail system with 

		/usr/init.d/mail stop 

	2) clear out the /usr/spool/mqueue directory of all 
		the current mail pending.

	3) configure sendmail (/usr/lib/sendmail.cf)

	4) restart mail with

		/usr/init.d/mail start



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Miguel (Michael) J. Sanchez
miguel@csd.sgi.com			
Member Technical Staff, Silicon Graphics, Inc.         

Daniel X Pape (dpape@imlab) wrote:
: I looked at a ps -e listing of the current processes...

: and there were at least 25 sendmail processes running.

  Try to use the mailq command to check if there are any mail items that are
waiting for delivery. If that is the case, it might indicate a sendmail which
is not properly configured, a wrong address or a connectivity problem. Anyway,
they should go away after a few minutes and start again after some time.

: What could cause sendmail to be run more than once? I thought that
: the only place that sendmail was invoked was by init on startup.

 If I am recalling correctly, there is a sendmail process for each outgoing
mail item.

: I've rebooted the machine a few times, and this doesn't seem to help.
: Killing all but one of the processes doesn't work either.

 Every time you reboot the machine, sendmail finds the defered mail and spawns
itself again. See the man-page for sendmail for more details.

: OH-- also when running osview.... there are alway around 60-70 graphics
: interrupts every second, and about 250-300 system interrupts a second.
: EVEN when the machine is just sitting there with only one user!!

 That doesn't seem like a high number to me.

: 	
: 	Problems... Problems...



: Dan Pape
--

-- Yaron.

In article <C17xuE.JM2@news.cso.uiuc.edu>, dpape@imlab (Daniel X Pape) writes:
|> OH-- also when running osview.... there are alway around 60-70 graphics
|> interrupts every second, and about 250-300 system interrupts a second.
|> EVEN when the machine is just sitting there with only one user!!

It looks like others have answered all but this one. I think the graphic
interrupts are caused by the screen refresh cycles: 60 or 72 times a second.
-------------------------------------------------------------------------
Stan Jensen, Systems Engineer                          stanj@corp.sgi.com
Silicon Graphics Inc., M/S 14L-120                    Phone:(415)390-5822
P.O. Box 7311, 1350 Charleston Road                   FAX:  (415)962-1589
Mt. View, CA  94039-7311                                "I (heart) Tonks"
-------------------------------------------------------------------------