Sponsored Content
Full Discussion: No concurrent login
Top Forums UNIX for Advanced & Expert Users No concurrent login Post 33795 by Neo on Sunday 19th of January 2003 10:51:40 PM
Old 01-19-2003
You could write a simple line in the login script that looks for a lock file, something like /etc/logins/lock_your_user_id and then if it does not exist, allow the login and then create the file. This is a simple file locking mechanism that is used a lot in UNIX systems and could be used here very easily.
 

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
logins(1M)						  System Administration Commands						logins(1M)

NAME
logins - list user and system login information SYNOPSIS
/usr/bin/logins [-admopstux] [-g group...] [-l login_name...] DESCRIPTION
This command displays information on user and system logins known to the system. Contents of the output is controlled by the command options and can include the following: user or system login, user id number, passwd account field value (user name or other information), primary group name, primary group id, multiple group names, multiple group ids, home directory, login shell, and four password aging param- eters. The default information is the following: login id, user id, primary group name, primary group id and the account field value. Out- put is sorted by user id, system logins, followed by user logins. OPTIONS
Options may be used together. If so, any login that matches any criteria are displayed. The following options are supported: -a Add two password expiration fields to the display. The fields show how many days a password can remain unused before it automatically becomes inactive, and the date that the password expires. -d Selects logins with duplicate uids. -g group Selects all users belonging to group, sorted by login. Multiple groups can be specified as a comma-separated list. When the -l and -g options are combined, a user is only listed once, even if the user belongs to more than one of the selected groups. -l login_name... Selects the requested login. Multiple logins can be specified as a comma-separated list. Depending on the nameservice lookup types set in /etc/nsswitch.conf, the information can come from the /etc/passwd and /etc/shadow files and other nameservices. When the -l and -g options are combined, a user is only listed once, even if the user belongs to more than one of the selected groups. -m Displays multiple group membership information. -o Formats output into one line of colon-separated fields. -p Selects logins with no passwords. -s Selects all system logins. -t Sorts output by login instead of by uid. -u Selects all user logins. -x Prints an extended set of information about each selected user. The extended information includes home directory, login shell and password aging information, each displayed on a separate line. The password information currently consists of password status: NP Account has no password LK Account is locked for UNIX authentication NL Account is a no login account PS Account probably has a valid password UN Account password status is unknown. That is, it is not a recognizable hashed password or any of the above entries. See crypt(3C) for valid password hashes. If the login is passworded, status is followed by the date the password was last changed, the number of days required between changes, and the number of days allowed before a change is required. The password aging information shows the time interval that the user receives a password expiration warning message (when logging on) before the password expires. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
passwd(1), crypt(3C), attributes(5) SunOS 5.11 6 Sep 2005 logins(1M)
All times are GMT -4. The time now is 08:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy