Thanks to those who responded on and off list.
It turns out the culprit was a Unix script that had been in production since
2001. The last line of this script had been commented out with an asterisk
instead of a pound sign... This was a harmless error, until last Thursday
when the script
Is this some kind of virus?
-Original Message-
From: mark.hennessey [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 12:21 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] UV - Available memory exceeded
You have received an important delivery from mark.hennessey
Please pick up
password for the
web server is donttellanyone!' to sail right through...
Mark
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jerry Banker
Sent: Monday, July 16, 2007 2:19 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UV - Available memory exceeded
Mark,
This is perhaps grasping at straws and likely not the cause,
but...
We've seen this type of behavior available memory exceeded
with (1) aborted resizes -- resize bits are left set and can cause
attempts to reopen the file in a loop, eventually filling up the stack
space,
Or monster large records, typically out of a type 1 or 19 file.
Example would be trying to ED PH GAZILLION_LINE_FILE.
--
Regards,
Clif
~~~
W. Clifton Oliver, CCP
CLIFTON OLIVER ASSOCIATES
Tel: +1 619 460 5678Web: www.oliver.com
