Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Status\s+Code\s+150s\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Status\s+Code\s+150s\s*$/: 2 ]

Total 2 documents matching your query.

1. [Veritas-bu] Status Code 150s (score: 1): Author: comp_geek_gal <netbackup-forum AT backupcentral DOT com>; Date: Sat, 05 Apr 2008 17:22:25 -0400; A quick note - typically bpsched 150's without intervention by admin can be caused by: - lack of swap (that's typically the reseason for the fork error) - lack of message queue space...bpsched messag; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2008-04/msg00086.html (11,368 bytes)
2. Re: [Veritas-bu] Status Code 150s (score: 1): Author: Justin Piszcz <jpiszcz AT lucidpixels DOT com>; Date: Sat, 5 Apr 2008 20:03:15 -0400 (EDT); I have never seen this personally but very good to know, thanks! Justin. _______________________________________________ Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu http://mailman.; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2008-04/msg00087.html (12,138 bytes)

Current List: 1 - 2
Page: [1]