@dba hard nofile 65535 @dba hard nproc 16384 @oaa hard nofile 65535 @oaa hard nproc 16384 is how Oracle recommends (with groups instead of users), I'm sure Sybase is similar. Also, you have "Sybase" as a user with a capital first letter. On 5/9/05, McDougall, Marshall (FSH) <MarMcDouga@xxxxxxxxx> wrote: > RH ES2.1, 2.4.21-15.ELsmp > > I am trying to give our DBA the ability to test his Sybase installation with > various parm changes, one of which is "ulimit -n". I have added: > > Sybase soft nofile 3072 > Sybase hard nofile 4096 > > to the /etc/security/limits.conf file and that sort of works. I say sort of > because if I log in as Sybase and execute ulimit -n 2048 I get: > > [sybase@fsh1166db02 sybase]$ ulimit -n > 1024 > [sybase@fsh1166db02 sybase]$ ulimit -n 2048 > -bash: ulimit: open files: cannot modify limit: Operation not permitted > > Then if I "su - sybase" and do it again, it works: > > [sybase@fsh1166db02 sybase]$ su - sybase > Password: > [sybase@fsh1166db02 sybase]$ ulimit -n 2048 > [sybase@fsh1166db02 sybase]$ ulimit -n > 2048 > > It's not making a lot of sense to me. Any enlightenment appreciated. > > Regards, Marshall > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
