Drew Parsons wrote:
> I'm not sure that I can see what the problem is.  ulimit -n 8192 does
> not run even when Xprt is not running, the limit it can be set to is -n
> 512, though higher values can be set as su.  As far as I can tell this
> behaviour is system controlled somewhere, not related to Xprt.  Can you
> really run ulimit -n 8192 after having removed xprint?
> 

Yes, i can. This is because i've added the following lines to
/etc/security/limits.conf:

*                soft    nofile          8192
*                hard    nofile          32768

I'm sorry for not stating this earlier.
I can now do this:

[EMAIL PROTECTED]:~$ ulimit -n 8192
[EMAIL PROTECTED]:~$ ulimit -n
8192

> Furthermore as far as I can tell 1024 is a standard ulimit for -n, at
> least it's reported as such by default from the bash command line
> (ulimit -a). 
> 
> As far other programs breaking, can you be more specific which ones?
> How much memory does your system have?

The first time i discovered it i was running an ant compile of my java
software project with many other terminals open on the desktop. I opened
some more terminals, and then the build failed even earlier.

Now after setting the ulimit higher, i can build again.

My memory right now looks like:

$ free -m
             total       used       free     shared    buffers     cached
Mem:          2008        924       1083          0         42        532
-/+ buffers/cache:        348       1659
Swap:         3812          0       3812

Also, i'm not sure if it's the right way to get the number of open
files, but here you go:

# lsof 2>/dev/null|wc -l
3471

> 
> If you want to sustain this bug, you'll need to convince me that Xprt is
> causing tangible problems.  How much system resources is it using?  What
> exactly is happening when your other programs break.  What is Xprt's
> open file usage? Measure it with "lsof | grep Xprt | wc" and compare
> with the total "lsof | wc".
> 

The problem is not Xprt or xprint itself, but that the ulimit is set too
low for my daily usage, in /etc/init.d/xinit
I'm unable to change it, and the values set in /etc/security/limits.conf
are ignored.

It sets both the hard and the soft limit (it should be enough to set the
soft limit, right?) without first checking if the hard and the soft
limit are not set higher already.


Thank you for your attention.

Christoffer Hammarström
[EMAIL PROTECTED]

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to