11-13-2015
Linux lock problem
Hi Team,
I have a requirement to access a shared resource from the user and interrupt context. What type of locking mechanism I have to use for this. Can any body give advice on this.
Thanks in advance.
-Shiva
8 More Discussions You Might Find Interesting
1. Programming
Hi,
I am trying to write stuff to a shared memory using a writer, and reading the corresponding stuff using a reader. I am facing problems while releasing the lock, as a result of which I am having segmentation faults. The code is as follows...
/********** writer.c ***********/
... (1 Reply)
Discussion started by: jacques83
1 Replies
2. Red Hat
hi friends
i have a small problem,in my redhat enterprise linux system screen lock is not working
if i click screen lock no action takes place...
so is there any solution to fix this problem or any alternate method available please let me know....
waiting for replys.......
thanks... (2 Replies)
Discussion started by: madhusudankh
2 Replies
3. Solaris
Hi,
I amnot able to execute any svm command. it gives the below message and hangs:
# metadetach d50 d30
metadetach: waiting on /etc/lvm/lock
^Cmetadetach: Interrupt
# metaclear d50
metaclear: waiting on /etc/lvm/lock
^Cmetaclear: Interrupt
Please advice.
Regards,
Sagar. (4 Replies)
Discussion started by: sag71155
4 Replies
4. Red Hat
Hi,
I want to lock the file in linux and the file cannot be edit or modify by other .I know in perl, there is function flock , but it is not worked.
The file can be modifed and edit even if it is locked by flock .
Any other way to lock the file and so other cannot edit or modifed it ????
Any... (7 Replies)
Discussion started by: chuikingman
7 Replies
5. Red Hat
Hello all,
If anyone has time, I have a few questions:
How do I do the following in Linux. We are using Red Hat and Oracle Enterprise Linux, which is based on Red Hat too.
1. How to lock the account after a few (like 3) invalid password attempts?
2. How do you lock a screen after 30... (1 Reply)
Discussion started by: nstarz
1 Replies
6. UNIX for Advanced & Expert Users
Hi all,
I have to test some user priviliges. The goal is to be sure that an unauthorized user can't restart some modules (ssh, mysql etc...).
I'm trying to automate it with a shell script but in same cases I got the syslog broadcast message.
Is there any way to simply get a return code... (3 Replies)
Discussion started by: Dedalus
3 Replies
7. UNIX for Dummies Questions & Answers
hi all
this s quite a foolish problem. I seem to hav pressed some keys s.t in unix, my letters are comin in caps and with caps lock on, i am getting lowercase letters. :o
Pls help.
Also is there any reference or manual where i can check in case such problems arrise?
thanx in advance
curiosity (4 Replies)
Discussion started by: curiosity
4 Replies
8. Red Hat
I'm having a weird problem with a RHEL6 workstation. When the screen lock is activated manually the system will lock and the screens will go blank. Once I try to unlock the system, the monitor will just flicker and won't respond. I tried the combination CTRL, ALT, Backspace and it did not work,... (4 Replies)
Discussion started by: goose25
4 Replies
LEARN ABOUT MINIX
posix_madvise
POSIX_MADVISE(3) Linux Programmer's Manual POSIX_MADVISE(3)
NAME
posix_madvise - give advice about patterns of memory usage
SYNOPSIS
#include <sys/mman.h>
int posix_madvise(void *addr, size_t len, int advice);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
posix_madvise():
_POSIX_C_SOURCE >= 200112L
DESCRIPTION
The posix_madvise() function allows an application to advise the system about its expected patterns of usage of memory in the address range
starting at addr and continuing for len bytes. The system is free to use this advice in order to improve the performance of memory
accesses (or to ignore the advice altogether), but calling posix_madvise() shall not affect the semantics of access to memory in the speci-
fied range.
The advice argument is one of the following:
POSIX_MADV_NORMAL
The application has no special advice regarding its memory usage patterns for the specified address range. This is the default
behavior.
POSIX_MADV_SEQUENTIAL
The application expects to access the specified address range sequentially, running from lower addresses to higher addresses.
Hence, pages in this region can be aggressively read ahead, and may be freed soon after they are accessed.
POSIX_MADV_RANDOM
The application expects to access the specified address range randomly. Thus, read ahead may be less useful than normally.
POSIX_MADV_WILLNEED
The application expects to access the specified address range in the near future. Thus, read ahead may be beneficial.
POSIX_MADV_DONTNEED
The application expects that it will not access the specified address range in the near future.
RETURN VALUE
On success, posix_madvise() returns 0. On failure, it returns a positive error number.
ERRORS
EINVAL addr is not a multiple of the system page size or len is negative.
EINVAL advice is invalid.
ENOMEM Addresses in the specified range are partially or completely outside the caller's address space.
VERSIONS
Support for posix_madvise() first appeared in glibc version 2.2.
CONFORMING TO
POSIX.1-2001.
NOTES
POSIX.1 permits an implementation to generate an error if len is 0. On Linux, specifying len as 0 is permitted (as a successful no-op).
In glibc, this function is implemented using madvise(2). However, since glibc 2.6, POSIX_MADV_DONTNEED is treated as a no-op, because the
corresponding madvise(2) value, MADV_DONTNEED, has destructive semantics.
SEE ALSO
madvise(2), posix_fadvise(2)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2017-09-15 POSIX_MADVISE(3)