10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
What I'm trying to do is write a script in Perl to find a user and if that user exist it would print "User Exist, Pls Try Again". If The user doesn't exist I'm able to create a user with a password.
Any suggestions? (3 Replies)
Discussion started by: GoBoyGo
3 Replies
2. UNIX for Dummies Questions & Answers
All the autosys jobs are on server-1 and server-1 has been crashed due to some reason, Now I have to run 5 autosys jobs on server-2 (failover server) which are on server 1.
How to do with Autosys command (which command needs to fired on JIL) (0 Replies)
Discussion started by: tp2115
0 Replies
3. Homework & Coursework Questions
first off let me introduce myself. My name is Eric and I am new to linux, I am taking an advanced linux administration class and we are tasked with creating a script to add new users that anyone can run, has to check for the existence of a directory. if the directory does not exist then it has... (12 Replies)
Discussion started by: pbhound
12 Replies
4. Ubuntu
Hi,
Anyone can help me on how to duplicate privileges and group for useroradb01 to userrootdb01. I have currently using "useroradb01" and create a newly user "userrootdb01".
I want both in the sames privileges and group. Please see the existing users list below;
drwxr-xr-x 53 useroradb01... (0 Replies)
Discussion started by: fspalero
0 Replies
5. HP-UX
HI Guys,
Can you help me creating a user account in a HP-UX server (3 Replies)
Discussion started by: Harikrishna
3 Replies
6. UNIX for Advanced & Expert Users
My project uses Autosys.
I am new to this product and I don't know where to start from.
Q1. Please provide me the link where I can get Autosys documentation
Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level) (0 Replies)
Discussion started by: gram77
0 Replies
7. HP-UX
I need to create new user from the root.which command can i used ? (2 Replies)
Discussion started by: magasem
2 Replies
8. UNIX for Dummies Questions & Answers
I created a user, i login as a root. I add him in the group where he can access and login as a root! I checked it in users' list and in group's list, he is there. My problem is this, I cant login using the username/account I just created! What should i do to use and login the user/account i've just... (5 Replies)
Discussion started by: jerome
5 Replies
9. UNIX for Advanced & Expert Users
Hi all,
I am using Sun Solaris 9 .In this system normal users unable to create files from the command line.I added these users in bin,adm and even root group i found them unable to create a file. (1 Reply)
Discussion started by: mallesh
1 Replies
10. UNIX Desktop Questions & Answers
who you can't log in as, but you can su over to them once you get on.
I am aware of how to make a no login user by using /NOSHELL in the spot for the shell in the passwd file, but my question is if I do that and then get on the box as a user who I can log in as and "su -" over to the nologin... (5 Replies)
Discussion started by: New_Guru
5 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)