Carisdad wrote:
[EMAIL PROTECTED] wrote:
No - it must have changed because of an applied patch. Perhaps 118855-15



No; it *must* be something you did.

Nothing ever set the limit to 1000 for both.

This persists across reboots.

Pool resource controls?

.files?
BTW Casper - can you update this item on the Solaris FAQ please.


About resource controls, you mean?

These settings should still work.

Please try "plimit" on all processes and see if a pattern emerges.

(And check /etc/project)

Casper

_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Actually, I think we're seeing something like this too, but without zones and 1024 fds, not 1000:

# plimit 172
172:    /usr/openv/netbackup/bin/bpjobd
  resource              current         maximum
 time(seconds)         unlimited       unlimited
 file(blocks)          unlimited       unlimited
 data(kbytes)          unlimited       unlimited
 stack(kbytes)         8192            unlimited
 coredump(blocks)      unlimited       unlimited
 nofiles(descriptors)  1024            1024
 vmemory(kbytes)       unlimited       unlimited

# grep rlim /etc/system
set rlim_fd_cur=32768

# cat /etc/project
system:0::::
user.root:1::::process.max-file-descriptor=(basic,32768,deny),(privileged,65536,deny)
noproject:2::::
default:3::::process.max-file-descriptor=(basic,32768,deny),(privileged,65536,deny)
group.staff:10::::

# uname -a
SunOS s0001 5.10 Generic_118822-25 sun4u sparc SUNW,Sun-Fire-V440

I've been having trouble getting a handle on this as well.

Are you seeing this for all processes?
Otherwise, it could be that the process has made a call to setrlimit()
and changed the default values...

-- Renaud


-Andy
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to