9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Please let me know how these steps are creating a lock file using echo " ".
LOCK_FILE=${LOG_DIR}/${DBNAME}_MD.lock
# create lock file
if
then
echo "Another process is running already. Will terminate this one." >> ${LOG_FILE} 2>&1
echo "If the lock file is not needed, please... (5 Replies)
Discussion started by: sandy162
5 Replies
2. Shell Programming and Scripting
Hi,
I am trying to create a lock file with the following code but for some reason after file is created it has
wrong name "PASP?.lock??"
Please let us know how to get rid of these '??' from file name and from where they are coming?
#!/bin/ksh... (6 Replies)
Discussion started by: sandy162
6 Replies
3. 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
4. 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
5. 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
6. UNIX for Dummies Questions & Answers
Hi,
We have a lock file being created called lck8c0001 created in Unixware 2.1.2. This is locking a printer.
According to some websites, 8c0001 relates to the device name.
How does one link 8c0001 to those devices listed in the /dev folder?
I have done a ps -lp for all printers and have... (4 Replies)
Discussion started by: canman
4 Replies
7. UNIX for Dummies Questions & Answers
how can I lock my keyboard while I'm away from the computer without using lock command. What other commands gives me the option to lock keyboard device?
thanks (7 Replies)
Discussion started by: dianayun
7 Replies
8. UNIX for Dummies Questions & Answers
I found a lock file like this
lrwxrwxr-x 1 sskb apollo 16 Oct 22 22:00 lock -> hostname:2747
(pl. note that hostname is a number like 123.4.5.6)
but this was not shown in the file manager eventhough I had selected to show the hidden files.
I could not even read the... (4 Replies)
Discussion started by: sskb
4 Replies
9. UNIX for Dummies Questions & Answers
We wish to keep a sequence number in a file. When someone wants to get the next sequence number we need to lock the file, get the next number and increment it by one. How do you do that?
I know how to get the number and increment it but how do I lock the file and test that it is locked or not... (1 Reply)
Discussion started by: tammy_schmuki
1 Replies
flock(2) System Calls Manual flock(2)
NAME
flock - Applies or removes an advisory lock on an open file
SYNOPSIS
#include <sys/fcntl.h>
int flock( int filedes, int operation );
PARAMETERS
Specifies a file descriptor returned by a successful open() or fcntl() function, identifying the file to which the lock is to be applied or
removed. Specifies one of the following constants for flock(), defined in the fcntl.h file: Apply a shared lock. Apply an exclusive lock.
Do not block when locking. This value can be logically ORed with either LOCK_SH or LOCK_EX. Remove a lock.
DESCRIPTION
The flock() function applies or removes an advisory lock on the file associated with the filedes file descriptor. Advisory locks allow
cooperating processes to perform consistent operations on files, but do not guarantee consistency (that is, processes may still access
files without using advisory locks, possibly resulting in inconsistencies).
You can use the flock() function to coordinate a file's lock status on local, CFS, and NFS file systems.
The locking mechanism allows two types of locks: shared locks and exclusive locks. At any time multiple shared locks may be applied to a
file, but at no time are multiple exclusive, or both shared and exclusive, locks allowed simultaneously on a file.
A shared lock may be upgraded to an exclusive lock, and vice versa, simply by specifying the appropriate lock type. This results in the
previous lock being released and the new lock applied (possibly after other processes have gained and released the lock).
Requesting a lock on an object that is already locked normally causes the caller to be blocked until the lock may be acquired. If LOCK_NB
is included in operation, then this will not happen; instead, the call will fail and errno will be set to [EWOULDBLOCK].
NOTES
Locks are on files, not file descriptors. That is, file descriptors duplicated using the dup() or fork() functions do not result in multi-
ple instances of a lock, but rather multiple references to a single lock. If a process holding a lock on a file forks and the child
explicitly unlocks the file, the parent will lose its lock.
Processes blocked awaiting a lock may be awakened by signals.
The flock() interface is not part of any UNIX standard. Therefore, if you are designing and writing applications to be portable across
platforms, you should use the fcntl() file locking interface instead of flock().
RETURN VALUES
Upon successful completion, 0 (zero) is returned. Otherwise, -1 is returned and errno is set to indicate the error.
ERRORS
If the flock() function fails, errno may be set to one of the following values: The file is locked and the LOCK_NB option was specified.
The filedes argument is not a valid open file descriptor. A signal interrupted the flock call. The operator is not valid. The lock table
is full. Too many regions are already locked. The lock is blocked by some lock from another process. Putting the calling process to
sleep while waiting for that lock to become free would cause a deadlock.
RELATED INFORMATION
Functions: close(2), exec(2), fcntl(2), fork(2), open(2), lockf(3) delim off
flock(2)