11-05-2004
The problem i found is that there's a missing line in the /etc/system..
Had to add the line:
set rlim_fd_max=4096
Without this condition, the default value for nofiles is half of the rlim_fd_cur.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i've encountered the following problem with sco unixware7.
after using the "ulimit -f unlimited" command and then using "ulimit -a" it lists the filesize as unlimited.
BUT, when type the ulimit command without parameters, the output is given as 4194303
so i can't create a file bigger than... (4 Replies)
Discussion started by: roydv
4 Replies
2. Shell Programming and Scripting
How do i set ulimit for user (4 Replies)
Discussion started by: Krrishv
4 Replies
3. SCO
hi,
i cant set ULIMIT for normal user (file size more than 2gb).but in root user it is working fine.in user it is giving error like "limit exceeded (priviledged user)". (2 Replies)
Discussion started by: prakrithi
2 Replies
4. UNIX for Advanced & Expert Users
I would like to set the maximum number or open files per process to be greater than 1024000 (for specific application scalability purpose). I am using RHEL 5.3/Ext4.
%sysctl fs.file-max
fs.file-max = 164766821
I also have added the folloing to /etc/security/limits.conf
* ... (7 Replies)
Discussion started by: Hsianglung Wu
7 Replies
5. Solaris
Hi All,
I get below error while running
cd /var/yp
/usr/sbin/ypinit -m
Error Code - 1
updated netmasks
make : warning : target all not remade because of errors
current working dir /var/yp
*** error code 1 ***
make : fatal error : command failed for target 'k'
error running... (4 Replies)
Discussion started by: naw_deepak
4 Replies
6. UNIX for Advanced & Expert Users
I changed the standard Ulimit sometime back. But when I change it back, the setting does not get updated.
How do I make the change permanent
Waitstejo (7 Replies)
Discussion started by: Waitstejo
7 Replies
7. UNIX for Advanced & Expert Users
All,
Our SA is considering setting the max open files from 2048 to 30K. This sounds like a drastic change. Does anybody have an idea of the negative impacts of increasing the open files too high? Would like to know if this change could negatively impact our system. What test should we run to... (2 Replies)
Discussion started by: wcrober
2 Replies
8. Red Hat
The root user runs the following
ulimit -a | grep open
and gets a result of
open files (-n) 8162
A user runs the same command and gets a result of
open files (-n) 2500
How can you set the ulimit of the user to... (2 Replies)
Discussion started by: jsanders
2 Replies
9. AIX
Hi,
Our application team is asking me to set ulimit parameter in my AIX 6.1 TL8 box.
Some of them i set already.
address space limit (kbytes) (-M) unlimited
locks (-L) unlimited
locked address space (kbytes) (-l) 64
nice (-e) ... (3 Replies)
Discussion started by: sunnybee
3 Replies
10. Solaris
A coredump is being created by one of our applications on Solaris server and occupying entire space on the mount, thereby bringing down the application.
While we try to identify the root cause, i tried to limit to limit the size of the core dump.
Executed below command in shell and also updated... (2 Replies)
Discussion started by: kesani
2 Replies
flaw(7) Miscellaneous Information Manual flaw(7)
NAME
flaw - a Lua OO management framework for awesome WM widgets
DESCRIPTION
flaw stands for Fully Loaded AWesome. It is a LUA object oriented library providing a thin abstraction layer above awesome widgets. It is
aimed at being simple and resources efficient.
To achieve these goals, flaw provides the following concepts.
gadgets
To add functionality to awesome widgets, flaw defines gadget objects, which are a wrapper around a widget. All gadgets have proper-
ties, events, a refresh mechanism and a data provider (see below). Gadgets can wrap all awesome widget type, namely text boxes,
image boxes, graphs or progress bars. flaw provides many gadgets for common system information (like CPU or memory activity).
provider
flaw tries to minimise system access and data refresh. Since all information do not have the same expiration rate, all gadgets
refresh independently. And since some gadgets can share information, all data is provided by providers which can be shared among
gadgets. Providers maintain status data from the system and refreshes only when necessary (ie. when the gadget with the shortest
refresh rate demands it).
events Events are a way for the user to modify the gadget behaviour or properties when some conditions are met. An event is composed of a
trigger, which computes the condition, and an action. Event triggers are tested by the providers only when data changes. Both the
condition and the action are provided by the user.
USAGE
flaw depends on the lua-filesystem package which can be found http://luaforge.net/projects/luafilesystem. Once installed, the following
statement must be inserted in awesome configuration before any flaw gadget or mechanism is used.
require('flaw')
Using flaw consists in creating gadgets, passing them parameters to customize their display and events to add some behaviour to them, and
then adding them in a wibox like any other awesome widget. flaw and awful gadgets can live together. The complete flaw documentation is
available in Luadoc format. Enter the following command to generate it.
LUA_PATH="path_toflaw/doclet/html/?;;" luadoc -d html --nofiles *.lua
DIAGNOSTICS
flaw tries to recover upon bad invocations. When something wrong occurs, it outputs warning or error messages to stderr (for example, if
awesome was started with xsession, output will be found in ~/.xsession-errors ).
BUGS
Certainly a lot.
AUTHOR
David Soulayrol <david.soulayrol at gmail dot net>
SEE ALSO
awesome(1), awesome-client(1), awesomerc(5)
FEBRUARY 2009 flaw(7)