03-07-2013
Yes, and severe swap is particularly nasty in that it can steal time from high-priority things indirectly. Stealing their memory now, means stealing their time later -- they'll go for their data and get a context switch instead. If you're burning a CD, that can mean coasters. Dealing with this in the OS itself is difficult since it adds so much overhead to each page operation though.
Linux supports voluntary measures for cache control, though. You can use madvise to tell the kernel you're done with a page, and so avoid cluttering up the cache with it.
9 More Discussions You Might Find Interesting
1. Linux
Hello!
How do make the limits.conf parameters work for a normal user. Ive changed
both the hard and soft parameter for the specific user. It used to be 4096 and i changed it to 16384. But when i use the ulimit -n, all i got is permissen denied.
Witch i can understand. But my question is? how... (1 Reply)
Discussion started by: dozy
1 Replies
2. UNIX for Dummies Questions & Answers
I have line in this file that says:
username - maxlogins 1
and user can login 2 times instad of one.
does enybody know why? and how can I fix that? (2 Replies)
Discussion started by: shooroop
2 Replies
3. HP-UX
Hi folks,
Hope you can help me. I have a process that is currently running at nice 20 and need it to run faster (-10?). How do I change the process using nice? I have the process number and thought it would be along the lines of;
nice -10 process_id
but it doesn't seem to like that. (1 Reply)
Discussion started by: gshuttleworth
1 Replies
4. UNIX for Advanced & Expert Users
HI,
To restrict the number of files and number of processes used the user we use the following configuration in the file /etc/security/limits.conf.
oracle soft nofile 65572
oracle hard nofile 65572
oracle soft noproc 16384
oracle soft noproc 16384
My question is what do the 'soft' and... (1 Reply)
Discussion started by: praveen_b744
1 Replies
5. Solaris
Hi,
How can we set per user core file size, etc in solaris, i.e. I want solaris counterpart/equivalent of linux /etc/security/limits.conf.
TIA (0 Replies)
Discussion started by: slash_blog
0 Replies
6. Red Hat
Hello all,
I'm running Oracle 10.2 on RHEL5. Current value of ulimit -n is set to a low value of 1024. I need to increase it to 65536 using the following procedure.
cat >> /etc/security/limits.conf <<EOF
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard... (3 Replies)
Discussion started by: luft
3 Replies
7. Red Hat
i want to set limits in /etc/security/limits.conf.My os is rhel 5.2.
It was giving continuous messages in in /var/log/secure like :
continuously.
I have changed values of priority and nice to "0" from unlimited and messages are not comming. But i want to know what is the ideal/maximum... (3 Replies)
Discussion started by: pankajd
3 Replies
8. Shell Programming and Scripting
Hello,
I am just starting with shell scripting, as everyone will soon see from my question. What I'm trying to do is call the Nice command to set the script process priority from /bin/ksh. The difference is I'm running it not directly through the shell, but through Bigfix (very similar to... (3 Replies)
Discussion started by: solly119
3 Replies
9. UNIX for Dummies Questions & Answers
OS version : RHEL 6.5
Below is an excerpt from /etc/security/limits.conf file for OS User named appusr in our server
appusr soft nproc 2047
appusr hard nproc 16384
What will happen if appusr has already spawned 2047 processes and wants to spawn 2048th process ?
I just want to know... (3 Replies)
Discussion started by: kraljic
3 Replies
LEARN ABOUT CENTOS
libtalloc_stealing
libtalloc_stealing(3) talloc libtalloc_stealing(3)
NAME
libtalloc_stealing - Chapter 2: Stealing a context
Stealing a context
Talloc has the ability to change the parent of a talloc context to another one. This operation is commonly referred to as stealing and it
is one of the most important actions performed with talloc contexts.
Stealing a context is necessary if we want the pointer to outlive the context it is created on. This has many possible use cases, for
instance stealing a result of a database search to an in-memory cache context, changing the parent of a field of a generic structure to a
more specific one or vice-versa. The most common scenario, at least in Samba, is to steal output data from a function-specific context to
the output context given as an argument of that function.
struct foo {
char *a1;
char *a2;
char *a3;
};
struct bar {
char *wurst;
struct foo *foo;
};
struct foo *foo = talloc_zero(ctx, struct foo);
foo->a1 = talloc_strdup(foo, "a1");
foo->a2 = talloc_strdup(foo, "a2");
foo->a3 = talloc_strdup(foo, "a3");
struct bar *bar = talloc_zero(NULL, struct bar);
/* change parent of foo from ctx to bar */
bar->foo = talloc_steal(bar, foo);
/* or do the same but assign foo = NULL */
bar->foo = talloc_move(bar, &foo);
The talloc_move() function is similar to the talloc_steal() function but additionally sets the source pointer to NULL.
In general, the source pointer itself is not changed (it only replaces the parent in the meta data). But the common usage is that the
result is assigned to another variable, thus further accessing the pointer from the original variable should be avoided unless it is
necessary. In this case talloc_move() is the preferred way of stealing a context. Additionally sets the source pointer to NULL,
thus.protects the pointer from being accidentally freed and accessed using the old variable after its parent has been changed.
Version 2.0 Tue Jun 17 2014 libtalloc_stealing(3)