Hi,

I'm not sure about 7 as I didn't test that, but they are aware
(LGTpa10486).
During process initialization NetWorker queries the OS Kernel for the
value 
of _CONFIG_OPEN_FILES. If the value returned to NetWorker is higher
then what 
is expected, nsrd and nsrexecd will fail to start, and produce a core
file. 

There are several articles on this subject by Legato.   In short, to
enable 
the fix you mentioned (setting ulimit to 2048) put that line in
/etc/init.d/NetWorker 
startup script (for Solaris), which will only change the environment
for NetWorker, 
and not any of the other applications.

It is necessary to understand the effect of setting unlimited file
descriptors on 
a system basis and that for some applications, such as NetWorker, this
has a 
negative effect mainly due to improper return values from the various
internal 
system calls. This should be configured on a application by
application basis 
and can be fixed by simple system administration tuning to have the
proper file 
descriptor number set to prevent the certain types of coredump. 

Cheers,
.c


-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] On Behalf Of Craig Ruefenacht
Sent: Thursday, October 16, 2003 8:14 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] rlim_fd_cur on Solaris and nsrexecd


Hi,

I haven't yet reported it to Legato.  I wanted to try and get some
feedback from the list first to make sure that what I was seeing was
correct.

I'm curios as to whether the bug exists in Networker 7.x.  We are on
Networker 6.1.3 and haven't had the need or desire to upgrade yet,
though we have the media and all.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=