Sponsored Content
Full Discussion: No concurrent login
Top Forums UNIX for Advanced & Expert Users No concurrent login Post 33866 by Neo on Wednesday 22nd of January 2003 08:28:08 AM
Old 01-22-2003
Quote:
Originally posted by champion
this seems to be a good idea. but when will the lock file be deleted? what if user just does not logout but plug out the electric power cable?
Naturally, you would have to clear the lock files when the system reboots after a crash. This is true for all programs that use lockfiles. You simply write a startup script that looks for and clears lock files when the system reboots.

As for logout actions, this is possible also. One possibility is to use the trap facility in the shell.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Definition of Concurrent Users

Can someone guide me in telling me what is a good definition of concurrent users. Is there a website I can go to to get this definition? (2 Replies)
Discussion started by: mpshaw
2 Replies

2. Filesystems, Disks and Memory

concurrent file access

Hi I am fairly new to the Unix environment and need to understand how Unix handles concurrent access to files and how it differs to Win NT. Any help would be greatly appriciated :) (1 Reply)
Discussion started by: beechwood
1 Replies

3. Shell Programming and Scripting

threads - concurrent processing

i have a program which uses a java thread that concurrently copies table data with many DB connections (one for each thread) new to unix, wanted to know if its possible to do a similar thing in a shell script. for eg script.sh trigger 2 stored procs at the same time which are... (6 Replies)
Discussion started by: siva_jm
6 Replies

4. Shell Programming and Scripting

Concurrent writing to file

Hi I have a ksh that can have multiple instances running at the same time. The script (each instance) uses the SAME log file to write to. Should this cause a problem or is the ksh clever enough to queue write requests to the file? Thanks. GMMIKE (2 Replies)
Discussion started by: GNMIKE
2 Replies

5. Shell Programming and Scripting

concurrent processes

We have a very large text file..contains almost 100K lines. We want to process this file to generate another text file as per our data requirement. As for now the parsing of data takes 20-25 mins each , for 100K lines. the current script uses : While Read Each Line do parsing.. Done ... (6 Replies)
Discussion started by: Amruta Pitkar
6 Replies

6. AIX

chvg -g on Concurrent VG

Hi, on normal (non concurrent) vgs, it's possible to extend a lun on san-storage , and use chvg -g to rewrite vgda, and use disks with the new size for lvm operations is the same procedure possbile on a hacmp-cluster (2 node in our case) with concurrent vgs in active/passive mode? cheers... (5 Replies)
Discussion started by: funksen
5 Replies

7. Linux

Is Concurrent I/O (CIO) available on Linux?

Hi Guys, I just wondering if any of the AIX gurus with some exposure to Linux Redhat can tell me whether in Linux ( Red Hat or OpenSuse ) we have a similar option/capability like the CIO (Concurrent I/O) which is currently available on AIX. The reason I'm asking is because in the past we... (2 Replies)
Discussion started by: arizah
2 Replies

8. Shell Programming and Scripting

Concurrent execution

Hi all, I have a folder with sql files that need to be inserted in a DB with SQL*Plus. The thing is that it takes too long to insert them all one by one, so I want to insert them five at a time. Currently what I use is this: for $FILENAME in *.sql do sqlplus -s $DBUSER@$SID << EOF ... (0 Replies)
Discussion started by: Tr0cken
0 Replies

9. Solaris

Increase concurrent logins?

Hi all, I've been tasked to create a robot account across a bunch of SunOS servers, amongst the requirements for this account is this condition: Concurrent access requirement The robot account shall have the ability to create at least ten(10) concurrent access sessions. In order to... (0 Replies)
Discussion started by: dan-e
0 Replies

10. AIX

Difference between concurrent and enhanced concurrent VG

Hi, What are the differences between concurrent and enhanced concurrent VGs.? Any advantages of enhanced concurrent VG over normal concurrent vg Regards, Siva (2 Replies)
Discussion started by: ksgnathan
2 Replies
SHELL-QUOTE(1p) 					User Contributed Perl Documentation					   SHELL-QUOTE(1p)

NAME
shell-quote - quote arguments for safe use, unmodified in a shell command SYNOPSIS
shell-quote [switch]... arg... DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands or files with embedded white space or shell globbing characters safely. Here are a few examples. EXAMPLES
ssh preserving args When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and passes them to "$SHELL -c". This doesn't work as intended: ssh host touch 'hi there' # fails It creates 2 files, hi and there. Instead, do this: cmd=`shell-quote touch 'hi there'` ssh host "$cmd" This gives you just 1 file, hi there. process find output It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote: eval set -- `find -type f -print0 | xargs -0 shell-quote --` debug shell scripts shell-quote is better than echo for debugging shell scripts. debug() { [ -z "$debug" ] || shell-quote "debug:" "$@" } With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can. save a command for later shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are things the user can't pass through), you can do something like this: user_switches= while [ $# != 0 ] do case x$1 in x--pass-through) [ $# -gt 1 ] || die "need an argument for $1" user_switches="$user_switches "`shell-quote -- "$2"` shift;; # process other switches esac shift done # later eval "shell-quote some-command $user_switches my args" OPTIONS
--debug Turn debugging on. --help Show the usage message and die. --version Show the version number and exit. AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions. AUTHOR
Roderick Schertler <roderick@argon.org> perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)
All times are GMT -4. The time now is 04:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy