**

Koyb:

 

Yes, I have had to reboot a server when the arserverd process grew too large for the system to handle it to increase the available program space.  Again, I stated that you may have to reboot the server if there is too much ‘lost’ memory either from the arserverd process or another process.  This should NEVER happen as all space should be reclaimed when/if you shutdown the arserverd process.

 

Also, you may have to reboot your server after applying server patches to correct problems encountered by Remedy processes.

 

James McKenzie

 

 


From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Koyb P. Liabt
Sent: Wednesday, May 03, 2006 1:57 PM
To: [email protected]
Subject: Fwd: Unix Server

 

Are these remedy patches?  Can't I start/stop the process and apply the patches. 

 

So has anyone been in a scenario where they had to reboot the server when there was no other resolution?

 

 

 

***************************************
I would reboot the server only if I applied server level patches or if there
was a memory leakage that could not be recovered by a restart of the ARS
server processes.  Otherwise, it is best to leave the server up and running.

James McKenzie

__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___

Reply via email to