At 17:55 -0800 2006/01/12, <[EMAIL PROTECTED]> wrote:
Never had a command stack big enough to cause problems.
This is a first for us too.
Since it's being called from the Unix command line could you not simply clear the stack prior to running the command?
That would take some coding changes because it's actually a service that calls UniData. I'll look at clearing the stack on the way out.
Or you could set the CSTACKSZ environment variable for this user so it won't get so big.
Unfortunately, that seems only to control the displayed stack depth. The problem eventually occurs even if CSTACKSZ is set to 5
We have a directory under UniData home called cmdstack and it puts all of the stacks in there so they work across all accounts. Not exactly sure how it was setup.
I'll have to look for that at the client site. Maybe a simple cron job would to the trick.
Ray -- .=================================================================. | =-=-=-=-=-=-= Eagle Rock Information Systems Corp =-=-=-=-=-=-= | | -=-=-=-=-=-=- web and database business solutions -=-=-=-=-=-=- | | <http://www.eriscorp.com> <mailto:[EMAIL PROTECTED]> | |Midwest Regional Office: 815-547-0662 (voice) 815-547-0353 (Fax)| .=================================================================. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
