Sponsored Content
Full Discussion: Linux lock problem
Top Forums UNIX for Advanced & Expert Users Linux lock problem Post 302960288 by shivakoteswarra on Friday 13th of November 2015 07:15:42 AM
Old 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

Problem with releasing semaphore lock

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

screen lock problem

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

/etc/lvm/lock problem

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

lock the file in linux

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

Security Question: Lock after invalid login, Session Lock and Required Minimum Password Length

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

Testing privileges -lock lockfile /var/lock/subsys/..- Permission denied

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

Caps lock problem

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

Problem with screen lock

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
MADVISE(2)						      BSD System Calls Manual							MADVISE(2)

NAME
madvise, posix_madvise -- give advice about use of memory SYNOPSIS
#include <sys/mman.h> int madvise(void *addr, size_t len, int advice); int posix_madvise(void *addr, size_t len, int advice); DESCRIPTION
The madvise() system call allows a process that has knowledge of its memory behavior to describe it to the system. The advice passed in may be used by the system to alter its virtual memory paging strategy. This advice may improve application and system performance. The behavior specified in advice can only be one of the following values: MADV_NORMAL Indicates that the application has no advice to give on its behavior in the specified address range. This is the system default behavior. This is used with madvise() system call. POSIX_MADV_NORMAL Same as MADV_NORMAL but used with posix_madvise() system call. MADV_SEQUENTIAL Indicates that the application expects to access this address range in a sequential manner. This is used with madvise() system call. POSIX_MADV_SEQUENTIAL Same as MADV_SEQUENTIAL but used with posix_madvise() system call. MADV_RANDOM Indicates that the application expects to access this address range in a random manner. This is used with madvise() system call. POSIX_MADV_RANDOM Same as MADV_RANDOM but used with posix_madvise() system call. MADV_WILLNEED Indicates that the application expects to access this address range soon. This is used with madvise() system call. POSIX_MADV_WILLNEED Same as MADV_WILLNEED but used with posix_madvise() system call. MADV_DONTNEED Indicates that the application is not expecting to access this address range soon. This is used with madvise() system call. POSIX_MADV_DONTNEED Same as MADV_DONTNEED but used with posix_madvise() system call. MADV_FREE Indicates that the application will not need the information contained in this address range, so the pages may be reused right away. The address range will remain valid. This is used with madvise() system call. MADV_ZERO_WIRED_PAGES Indicates that the application would like the wired pages in this address range to be zeroed out if the address range is deallocated without first unwiring the pages (i.e. a munmap(2) without a preceding munlock(2) or the application quits). This is used with madvise() system call. The posix_madvise() behaves same as madvise() except that it uses values with POSIX_ prefix for the advice system call argument. RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error. ERRORS
madvise() fails if one or more of the following are true: [EINVAL] The value of advice is incorrect. [EINVAL] The address range includes unallocated regions. [ENOMEM] The virtual address range specified by the addr and len are outside the range allowed for the address space. LEGACY SYNOPSIS
#include <sys/types.h> #include <sys/mman.h> int madvise(caddr_t addr, size_t len, int advice); int posix_madvise(caddr_t addr, size_t len, int advice); The include file <sys/types.h> is necessary. The type of addr has changed. SEE ALSO
mincore(2), minherit(2), mprotect(2), msync(2), munmap(2), compat(5) HISTORY
The madvise function first appeared in 4.4BSD. The posix_madvise function is part of IEEE 1003.1-2001 and was first implemented in Mac OS X 10.2. BSD
June 9, 1993 BSD
All times are GMT -4. The time now is 04:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy