This is happening on Ubuntu Release 12.04 (precise) 64-bit Kernel Linux 3.2.0-25-virtual
I'm trying to increase the number of open files allowed for a user.
Hi all,
How much we can increase fd-limit (file descriptor) in ubuntu for both 32-bit and 64-bit machine?
I am using ubuntu-10.04.
Can any one explain detail steps to increase fd-limit?
Thanx,
v16
Assume the OS is linux. Suppose I opened a file for write and get a file descriptor fdw. Is it possible to get another file descriptor fdr, with read-only access to the file without calling open again?
When you open a file, the kernel follows the link, and assigns the inode a file descriptor (a number that it keeps track of internally). When you delete the file, you are "unlinking" the inode; the file descriptor still points to it.
I'm working on an old legacy application, and I commonly come across certain settings that no one around cam explain.
Apparently at some point, some processes in the application were hitting the max number of files descriptors allowed per process, and the then team decided to increase the limit by adding the following to the init files of their shells (.kshrc):
((nfd=16#$(/etc/sysdef | grep "fil
My Apache is throwing Internal Server Error 500 errors and logs like this:
> [Sun Apr 07 23:35:24 2013] [error] [client 124.162.30.45] (2)No such
> file or directory: FastCGI: failed to connect to server
> "/home/magda_00aa/sportxxx.pl/sportxxx.pl.0fake": socket file
> descriptor (1063) is larger than FD_SETSIZE (1024), you probably need
> to rebuild Apache with a larger FD_SETSIZE
i want to increase the log limit of the varnish cache server , as i see when i write the log to a file it only give me about 13k of requests , i want to increase it to something like 1 million for a high traffic site , so i can save the log every 10 mins .
i know varnish can run as Demon and write the logs on run time , but i don't need this
so is there anyway to increase the varnish log limit
I'm having an issue with mysql 5.5 running on Ubuntu 12.04 with the open-files-limit parameter.
I recently noticed some problems due to the 1024 limit, and actually the main system limit was set to 1024, so I modified /etc/security/limits.conf with the following:
* soft nofile 32000
* hard nofile 32000
root soft nofile 32000
root hard nofile 32000
After that I check the ulimit value for root
It is well known that UNIX systems won't actually delete a file on disk while the file is in use.
Email this page
