09-21-2010
If this is true for any user, then create a dummy user. Alter /etc/profile
to recognize that user only, t o set tracing on. You can at least detect where a hang, if any, occurs when you login as dummy.
It almost has to be software/shell script related, if it were hardware or filesystems then the problem would occur under other circumstances.
If that shows nothing then PAM is your next target for investigation.
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I have some questions regarding disk perfomance, and what I can do to make it just a little (or much :)) more faster.
From what I've heard the first partitions will be faster than the later ones because tracks at the outer edges of a hard drive platter simply moves faster. But I've also read in... (4 Replies)
Discussion started by: J.P
4 Replies
2. AIX
Can I change any AIX System paramerter for speeding the data Disk performance?
Currently it slows with writing operations. (1 Reply)
Discussion started by: gogogo
1 Replies
3. AIX
Hello,
I have a aix 570 system with san disk. I do write test of performance
in a lv with four disk. While the test I run filemon tools for trace
the disk activity. The outputs of filemon are at the en of this message. I
see my lV(logical volume) throughput at 100 meg by second. 2 of 4
disk... (0 Replies)
Discussion started by: Hugues
0 Replies
4. AIX
I'm search for a disk exerciser / load tool like iometer, iozone, diskx for IBM AIX 5.2 and 5.3
Because of a very bad disk performance on several AIX systems, I need to have a tool which is able to generate a disk load on my local and SAN disks.
Does somebody knows a kind of tool which is... (5 Replies)
Discussion started by: funsje
5 Replies
5. Red Hat
I am getting absolutely dreadful iowait stats on my disks when I am trying to install some applications.
I have 2 physical disks on which I have created 2 separate logical volume groups and a logical volume in each. I have dumped some stats as below
My dual core CPU is not being over utilised... (3 Replies)
Discussion started by: jimthompson
3 Replies
6. Solaris
Dear All,
I have a hard disk in solaris on which the write performanc is too slow.
The CPU , RAM memory are absolutely fine.
What might be reason.
Kindly explain.
Rj (9 Replies)
Discussion started by: jegaraman
9 Replies
7. Solaris
What tools/utilities do you use to generate metrics on disk i/o throughput on Solaris. For example, if I want to see the i/o rate of random or sequential r/w. (2 Replies)
Discussion started by: dangral
2 Replies
8. Solaris
Hello,
we have a machine with Solaris Express 11, 2 LSI 9211 8i SAS 2 controllers (multipath to disks), multiport backplane, 16 Seagate Cheetah 15K RPM disks.
Each disk has a sequential performance of 220/230 MB/s and in fact if I do a
dd if=/dev/zero of=/dev/rdsk/<diskID_1> bs=1024k... (1 Reply)
Discussion started by: golemico
1 Replies
9. Linux
I have a freshly installed Oracle Linux 7.1 ( akin to RHEL ) server.
However after installing some Oracle software, I have noticed that my hard disk light is continually on and the system performance is slow.
So I check out SAR and IOSTAT
lab3:/root>iostat
Linux... (2 Replies)
Discussion started by: jimthompson
2 Replies
LEARN ABOUT DEBIAN
calife
CALIFE(1) BSD General Commands Manual CALIFE(1)
NAME
calife -- becomes root (or another user) legally.
SYNOPSIS
calife [-] [login]
or
... [-] [login] for some sites (check with your administrator).
DESCRIPTION
Calife requests user's own password for becoming login (or root, if no login is provided), and switches to that user and group ID after veri-
fying proper rights to do so. A shell is then executed. If calife is executed by root, no password is requested and a shell with the appro-
priate user ID is executed.
The invoked shell is the user's own except when a shell is specified in the configuration file calife.auth.
If ``-'' is specified on the command line, user's profile files are read as if it was a login shell.
This is not the traditional behavior of su.
Only users specified in calife.auth can use calife to become another one with this method.
You can specify in the calife.auth file the list of logins allowed for users when using calife. See calife.auth(5) for more details.
calife.auth is installed as /etc/calife.auth.
FILES
/etc/calife.auth List of users authorized to use calife and the users they can become.
/etc/calife.out This script is executed just after getting out of calife.
SEE ALSO
su(1), calife.auth(5), group(5), environ(7)
ENVIRONMENT
The original environment is kept. This is not a security problem as you have to be yourself at login (i.e. it does not have the same security
implications as in su(1) ).
Environment variables used by calife:
HOME Default home directory of real user ID.
PATH Default search path of real user ID unless modified as specified above.
TERM Provides terminal type which may be retained for the substituted user ID.
USER The user ID is always the effective ID (the target user ID) after an su unless the user ID is 0 (root).
BUGS
The MD5-based crypt(3) function is slower and probably stronger than the DES-based one but it is usable only among FreeBSD 2.0+ systems.
HISTORY
A calife command appeared in DG/UX, written for Antenne 2 in 1991. It has evolved considerably since this period with more OS support, user
lists handling and improved logging.
PAM support was introduced in 2005 to port it to MacOS X variants (Panther and up).
AUTHOR
Ollivier Robert <roberto@keltia.freenix.fr>
BSD
September 25, 1994 BSD