01-16-2003
No concurrent login
Hi,
I notice in my Sun Solaris 8 sparc workstatin, I am able to login concurrently using a same user ID.
Is there a way to disallow this? That is, at anyone time, the user can have only 1 login session.
How can it be done?
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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
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
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
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
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
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
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
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
GETLOGIN(2) BSD System Calls Manual GETLOGIN(2)
NAME
getlogin, setlogin -- get/set login name
SYNOPSIS
#include <unistd.h>
char *
getlogin(void);
int
setlogin(const char *name);
DESCRIPTION
The getlogin() routine returns the login name of the user associated with the current session, as previously set by setlogin(). The name is
normally associated with a login shell at the time a session is created, and is inherited by all processes descended from the login shell.
(This is true even if some of those processes assume another user ID, for example when su(1) is used.)
Setlogin() sets the login name of the user associated with the current session to name. This call is restricted to the super-user, and is
normally used only when a new session is being created on behalf of the named user (for example, at login time, or when a remote shell is
invoked).
RETURN VALUES
If a call to getlogin() succeeds, it returns a pointer to a null-terminated string in a static buffer. If the name has not been set, it
returns NULL. If a call to setlogin() succeeds, a value of 0 is returned. If setlogin() fails, a value of -1 is returned and an error code
is placed in the global location errno.
ERRORS
The following errors may be returned by these calls:
[EFAULT] The name parameter gave an invalid address.
[EINVAL] The name parameter pointed to a string that was too long. Login names are limited to MAXLOGNAME (from <sys/param.h>)
characters, currently 12.
[EPERM] The caller tried to set the login name and was not the super-user.
SEE ALSO
setsid(2)
BUGS
Login names are limited in length by setlogin(). However, lower limits are placed on login names elsewhere in the system (UT_NAMESIZE in
<utmp.h>).
In earlier versions of the system, getlogin() failed unless the process was associated with a login terminal. The current implementation
(using setlogin()) allows getlogin to succeed even when the process has no controlling terminal. In earlier versions of the system, the
value returned by getlogin() could not be trusted without checking the user ID. Portable programs should probably still make this check.
HISTORY
The getlogin() function first appeared in 4.4BSD.
4.2 Berkeley Distribution June 9, 1993 4.2 Berkeley Distribution