Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+dsmserv\.err\s+not\s+being\s+written\s+to\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+dsmserv\.err\s+not\s+being\s+written\s+to\s*$/: 3 ]

Total 3 documents matching your query.

1. [ADSM-L] dsmserv.err not being written to (score: 1): Author: "Minns, Farren - Chichester" <fminns AT WILEY DOT COM>; Date: Thu, 22 Sep 2011 09:15:05 +0100; Hi all I am still trying to figure out why I'm seeing intermittent drive faults, but have noticed that the dsmserv.err log is not getting written to (and hasn't been for a long time). TSM 5.5.2.0 on; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-09/msg00126.html (11,610 bytes)
2. Re: [ADSM-L] dsmserv.err not being written to (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Thu, 22 Sep 2011 07:41:22 -0400; It's not an issue: the server error log is for recording thread and process termination events. The Activity Log records hardware events, which supplements your operating system error logging and any; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-09/msg00127.html (11,131 bytes)
3. Re: [ADSM-L] dsmserv.err not being written to (score: 1): Author: "Minns, Farren - Chichester" <fminns AT WILEY DOT COM>; Date: Thu, 22 Sep 2011 12:49:54 +0100; Ah ok, thanks Richard Farren It's not an issue: the server error log is for recording thread and process termination events. The Activity Log records hardware events, which supplements your operating; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-09/msg00128.html (11,951 bytes)

Current List: 1 - 3
Page: [1]