I understand the ulimit values.  Back to my question on what limits/values
should we be setting?  I have seen various suggestions of which one said
4096 but that isn't working......

On Wed, Apr 17, 2013 at 9:32 AM, Richard Sims <rbs AT bu DOT edu> wrote:

> On Apr 17, 2013, at 9:16 AM, Zoltan Forray <zforray AT VCU DOT EDU> wrote:
>
> > Speaking of tuning, I have a question about Linux kernel parameters.
> >
> > Back a while ago we started having intermittent problems running a DB
> > backup on one of our V6 systems.  From what I posted here, a responder
> with
> > the same problem came upon some documentation listing recommended kernel
> > parms for Linux servers and DB2.
> >
> > So my OS guy went around to all of our TSM servers and set the nofiles
> > value to 4096, along with other recommended tuning parms.
> >
> > Now we are see this message on most of our servers:
> >
> > ANR3619W The user limit for open files is below the recommended minimum
> > value of 4096.
> >
> > eventhough IT IS set to 4096
>
> Well, the nofile parameter in /etc/security/limits.conf is the maximum
> value the usernamed process may use. That is not necessarily what the
> process has set via the 'limit' or 'ulimit' command. This is what is know
> in Unix as Resource Limits, where there is a ceiling, and there is a
> currently defined value which the process has chosen to use.
> See also APAR IC90127.
>
>     Richard Sims
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html