This is how append to Log files in UV: some of the log files get to
be many hundreds of megabytes and this is still fast:
% -
subroutine APPEND.UNIX(NEW.LINE, PATH, ERR)
ERR = '' ;* Return this if nothing goes wrong
openseq PATH to SEQFILE else
Also, could you confirm that your VOC _PH_ is in fact a DIR-type?
Yes sir, it is a DIR-type file.
-Kevin
[EMAIL PROTECTED]
http://www.PrecisOnline.com
** Check out scheduled Connect! training courses at
http://www.PrecisOnline.com/train.html.
---
u2-users mailing list
Adrian, normally I would agree with you, sequential file output SHOULD
be more efficient. However, because this isn't your typical WRITESEQ
type situation - the output is coming from PRINT statements - my
theory is that the rules may be different. And if I hadn't seen this
thing get wacky at
October 2006 12:48 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [UD] Weird Logging Issue
I suspect you are right, but consider that you are writing to a
sequential file when you use the PH file as a 'log' file. Handling
that much data in an ongoing process will fill up the memory space
I suspect you are right, but consider that you are writing to a sequential
file when you use the PH file as a 'log' file. Handling that much data
in an ongoing process will fill up the memory space assigned to the
phantom process. At least that's my story...
I would recommend actually opening up
I would recommend actually opening up
an item in a file, counting the number
of lines in the file (with a routine to
delete the top of the file as it grows
beyond a useful size) and then doing:
I'd love to implement more elegant logging, but as this is a
vendor-written process, my options are
I've seen similar erratic behavior when a phantom process set locks for
a possible update, but then didn't clear the lock when no update
occurred. I'm suggesting you have a locking issue but the out of memory
behavior is identical - it waits for available memory before it can
perform the next
Corrected posting - sorry...
I've seen similar erratic behavior when a phantom process set locks for
a possible update, but then didn't clear the lock when no update
occurred. I am NOT suggesting you have a locking issue but the out of
memory behavior is identical - it waits for available
Hi Kevin,
What O/S?
_PH_ is a DIR-type file, so your issue could be O/S-related.
Also, could you confirm that your VOC _PH_ is in fact a DIR-type? If a
record reaches 3MB in a hashed file, every multivalued database I've
worked with gets cranky.
Hope this helps,
Tom
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, 11 October 2006 12:48 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [UD] Weird Logging Issue
I suspect you are right, but consider that you are writing
10 matches
Mail list logo
