jbjohnso ae1cb4d55b -Be more forgiving of issues at close session time, since a need for retries on close session is more often than not indicative that no response will ever come back. ... -Go through the standard number of retries, but do it at one second intervals to get them out of the way faster (in the unlikely scenario that the request was dropped by the ethernet fabric, this should still get the session reaped) -Ignore a failure to get a command response for close session -The worst scenario that a user is not warned about is the slight possibility that a session slot on the BMC is not freed and instead will consume the slot for about a minute. Since we try to keep the number of sessions to a BMC down, one consumed meaninglessly for a minute in a rare case is not a huge problem git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@4295 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd		2009-10-05 15:05:29 +00:00
..
dsh/Context
monitoring	porting start_RRD_server&stop_RRD_server to linux	2009-07-04 03:59:42 +00:00
plugins	-Be more forgiving of issues at close session time, since a need for retries on close session is more often than not indicative that no response will ever come back.	2009-10-05 15:05:29 +00:00
schema/samples
shfunctions