>
>
> Maybe I'm wrong, but I don't think that /proc/sys/fs/inode-nr means so,
> looks like /proc/sys/fs/file-nr is the one you are looking for.
>
> I've found this:
> http://www.cs.tau.ac.il/~didi/file-nr.html
>
>
That is true, but I allways thought that you also need to change the
per/proces
* Cuenta la leyenda que Donovan Baarda ([EMAIL PROTECTED]) escribió:
> On Fri, 2003-05-09 at 03:43, Russell Coker wrote:
> > On Fri, 9 May 2003 02:55, Matthew Walkup wrote:
> > > 2) Is there a way to see what the current number of real open files are?
> > > lsof reports all open sockets, etc, so I'
I am latching on the tail end of this thread.
I ran the command on my IMAP server with 200 users logged in.
[EMAIL PROTECTED]:~$ cat /proc/sys/fs/inode-nr
210202 35354
a few secs later
[EMAIL PROTECTED]:~$ cat /proc/sys/fs/inode-nr
210229 35354
I guess I l have a ulimit set to low here ?
[E
On Fri, 9 May 2003 10:22, Donovan Baarda wrote:
> > cat /proc/sys/fs/inode-nr
>
> 10:19:33 [EMAIL PROTECTED]:~
> $ cat /proc/sys/fs/inode-nr
> 32189 20527
>
> I'm guessing this means my system has 20527 files open out of a maximum
> allowed 32189.
>
> That's quite a bit more than I expected, give
On Fri, 2003-05-09 at 03:43, Russell Coker wrote:
> On Fri, 9 May 2003 02:55, Matthew Walkup wrote:
> > 2) Is there a way to see what the current number of real open files are?
> > lsof reports all open sockets, etc, so I'm not sure how.
>
> cat /proc/sys/fs/inode-nr
10:19:33 [EMAIL PROTECTED]:~
On Fri, 9 May 2003 02:55, Matthew Walkup wrote:
> 2) Is there a way to see what the current number of real open files are?
> lsof reports all open sockets, etc, so I'm not sure how.
cat /proc/sys/fs/inode-nr
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www
Anyone have an answer to my second question:
2) Is there a way to see what the current number of real open files are?
lsof reports all open sockets, etc, so I'm not sure how.
I'm guessing the proper way is:
lsof | grep REG | wc -l
1809
Thanks,
Matt
-Original Message-
From: Matthew Wa
On Thu, May 01, 2003 at 11:32:57PM +0200, Thomas Lamy wrote:
>
> Or, fix file descriptor leaks on your perl script. I have yet to see a web
> server crawling on fd limits.
You take a busy homepage server, also a couple of customers who want
to make money by using there free webspace for pr0n-hosti
@lists.debian.org
Subject: Re: Open File Limit
Rus Foster wrote:
>
> On Thu, 1 May 2003, Matthew Walkup wrote:
>
> > However, every morning, I run a Perl script that processes
> all of my apache
> > logs into webalizer. I believe it is this script, that
> cause me to get
>
On Friday, May 02, 2003 1:15 AM [GMT+0800=SGT],
Matthew Walkup <[EMAIL PROTECTED]> wrote:
> May 1 08:50:26 a-web pop3d[14225]: connect from x.x.x.x
> May 1 08:50:26 a-web pop3d[14225]: error: cannot execute
> /usr/sbin/pop3d: Too many open files in system
> May 1 08:51:05 a-web pop3d[14346]: co
Rus Foster wrote:
>
> On Thu, 1 May 2003, Matthew Walkup wrote:
>
> > However, every morning, I run a Perl script that processes
> all of my apache
> > logs into webalizer. I believe it is this script, that
> cause me to get
> > several errors in the /var/log/daemon.log (The cron.daily is run
On Thu, 1 May 2003, Matthew Walkup wrote:
> However, every morning, I run a Perl script that processes all of my apache
> logs into webalizer. I believe it is this script, that cause me to get
> several errors in the /var/log/daemon.log (The cron.daily is run at
> 06:25:00):
> May 1 06:32:40 a-w
12 matches
Mail list logo
