03-10-2008
No idea if this has been already solved, but if not.. here's the hint..
change the owner of the files to root.For all other users , to write to the file, scripts should be executed using the "Sudo" command.
You may also need to add the names of the scripts which would be used for writing in the files to the sudoers file.
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. 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
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 Advanced & Expert Users
I have an Essbase installation on Solaris 10 and need to get the backups configured. Unfortunately several key files are locked and Essbase (OLAP application) is not releasing the locks when the Essbase or the applications within stop running. It appears I can use chmod to unlock the files but I... (0 Replies)
Discussion started by: JavaBrian
0 Replies
7. 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
8. 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
9. 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
10. Shell Programming and Scripting
Hello,
I have been working on using "flock"/file lock to prevent two instances of a bash script from being executed. Below is a simplified version of what I have to illustrate the flock part. It works as it is set up there below however the piece I am trying to figure out is how to get it to... (2 Replies)
Discussion started by: infrared013
2 Replies
cvslock(1) User Manuals cvslock(1)
NAME
cvslock - lock CVS repositories
SYNOPSIS
cvslock [-q] [-p pid] [-d CVS root] [-R|-W] [-u|-s|-c Command] [-l] directory
DESCRIPTION
cvslock is used to lock a tree starting at directory in your CVS repository during low-level manipulation or inspection.
There are various modes of operation: You can use the -s or -c options to cause cvslock to spawn a sub-shell or a shell command from which
you can safely access the source repository.
You can also use cvslock to lock and unlock CVS repositories from shell scripts; in this case you'll want to use the -p option to specify
the process ID which is written to the lock files' names.
The default when given no options is to acquire a persistant read lock.
OPTIONS
-q This option tells cvslock to shut up and not print any diagnostic messages to stdout. This is most useful when using the program in
conjunction with, e.g., rsync(1).
-p pid The CVS lock files generated by this utility have the current process ID in their name to distinguish them from lock files generated
by other tools such as cvs itself or concurrent sessions of cvslock. Use this option to force cvslock to use a specific pid. This
is in most useful from shell scripts.
-d CVS root
This optional argument tells cvslock where your CVS repository's root is. If no -d switch is given, cvslock will fall back to the
CVSROOT environment variable. Note that cvslock only works on local repositories, so don't try to access pserver or rsh-accessible
remote repositories this way.
-R This switch tells cvslock to acquire a lock for safe reading of the repository.
-W This switch tells cvslock to acquire a write lock on the repository.
-s When invoked with this option, cvslock will invoke the user's login shell as determined by the SHELL environment variable after
locking the repository. After the user has left that shell, cvslock will drop the locks.
-c Command
This option is similar to the -s option, with the difference that cvslock will execute the shell command given on the command line
instead of giving the user an interactive shell.
-u When given this option, cvslock will try to drop a previously created lock on the repository in question. Using this option
together with the -s or -c options is an error. The use of -p is highly recommended in conjunction with this option!
-l This option tells cvslock to lock only the directory specified. Normally it locks the entire directory hierarchy under the speci-
fied directory.
DIAGNOSTICS
cvslock spits out some diagnostics to the standard error stream. It's exit value is zero if and only if the locking operation requested by
the user could be performed successfully. Note that no diagnostics about the exit value of commands executed through the -c switch are
given.
BUGS
The signal handling is not too well-tested and may be broken.
If you try to create the same lock several times, you will get funny effects due to the error recovery cvslock tries to do.
SEE ALSO
Version Management with CVS
rsync(1), system(3), cvs(1)
AUTHOR
cvslock was put together in a quick hacking session by Thomas Roessler <roessler@guug.de> and may be distributed under the terms of the GNU
General Public License version 2.
Unix October 1998 cvslock(1)