02-10-2005
AIX 4.3.3 takes forever to log in
Hi all, my RS/6k 7043 150 with aix 4.3.3 takes FOREVER to log in. When I power the machine on, the boot process procedes normally and I get 2 short beeps (which I don't recall hearing before) and then I get the login window. If I log in, as root, say, the machine goes to its usual blue screen which says something like "Starting the Common Desktop Environment" and it sits on this screen for what seems like forever. Eventually, I do get logged in (after something like half an hour). If I do a command line login or a failsafe login, I get logged in very quickly. Can anyone give me any advice as to how to troubleshoot this problem?
Thanks for the help. Jeff
9 More Discussions You Might Find Interesting
1. Programming
When I am using msgrcv to get a message from a queue, in case of msgsnd some error, the msgrcv thread will waiting forever.
Is there some way that I can specify a time out value for this queue ? just let msgrcv wait for some time, if no message comes during this time slot, msgrcv just return... (3 Replies)
Discussion started by: Yun Gang Chen
3 Replies
2. Solaris
Hi I am very new for Solaris, I want to make some users' passwords never expired. My ssytem kernel is: 5.8
# uname -a
SunOS sspfs_svr 5.8 Generic_117000-01 sun4u sparc SUNW,Netra-240
Could you make some advice?
Thanks (5 Replies)
Discussion started by: xramm
5 Replies
3. UNIX for Dummies Questions & Answers
Hello all
i found out about the sar command but when looking in the man pages
there is no way to make sar working for ever .. only
with some kind of interval . like sar 2 30 .
my question is can i just run sar for ever ? (5 Replies)
Discussion started by: umen
5 Replies
4. Linux
Hi guys! I've just mounted my drive in fstab:
/dev/sdb /myfolder ext3 defaults 0 0
and rebooted linux.
I've got severel failers during booting process and also I can't login as root first time:
login: root
password:root
incorrect login
login:user
password: user
... (1 Reply)
Discussion started by: Junior Admin
1 Replies
5. IP Networking
Just looking at my ethernet interface.. I see this response... what does this mean...?
ipconfig...
lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft... (0 Replies)
Discussion started by: jimmyc
0 Replies
6. Shell Programming and Scripting
I'm trying to make a little script, but I have a problem...
I'm trying to sed a list of files made with a ls > filename.txt...
Two variables (or i may call them constant because they are fixed values :D):
ststr1 and ststr2
I want to
sed s/"$ststr1"/"$ststr2"/g filename.txt >... (5 Replies)
Discussion started by: maxlamax
5 Replies
7. Programming
looking in pthread's source code I can see that as an epilogue both pthread_cond_timedwait and pthread_cond_wait will try to relock the mutex by means of __pthread_mutex_cond_lock.
Does this mean that any of them both could eventually block forever if the mutex is never again available after... (4 Replies)
Discussion started by: ramestica
4 Replies
8. Red Hat
Hello All,
I was trying to install one rpm and it failed due to missing dependencies, when I try to look at the dependencies and try to install them it is asking for 100+ dependencies, did any one ever face this problem? how can we fix this?
rpm -ivh /var/tmp/erlang-R15B-02.1.el6.x86_64.rpm... (0 Replies)
Discussion started by: lovesaikrishna
0 Replies
9. UNIX for Dummies Questions & Answers
I am trying to use the forever command. I can get it to work if I do not use the w option to watch for changes and cause an automatic restart on a change to the contents of the directory being watched.
I would really like to use the watch option. Is this option fully implemented? here is an... (4 Replies)
Discussion started by: barrygordon
4 Replies
halt(8) System Manager's Manual halt(8)
NAME
halt - Stops the processor
SYNOPSIS
/usr/sbin/halt [-d] [-l] [-n] [-q] [-y]
DESCRIPTION
If other users are logged into the system, or if the system is operating at a multiuser run level, use the /usr/sbin/shutdown -h command to
halt the system. If only the root user is logged in, and you do not plan to restart the system immediately, use the halt command.
The halt command writes data to the disks and then stops the processor(s), but does not reboot the machine. You must be the root user to
run this command.
When the system displays the ....Halt completed.... message, you can turn off power to the machine.
If the command is invoked without the -l, -n, or -q flag, the halt program logs the shutdown using the syslogd command and places a record
of the shutdown in the login accounting file, /var/adm/wtmp. Using the -q and the -n flags imply the -l flag.
FLAGS
Generates a crash dump of the system before halting it. Can be used with any other flag. Does not log the halt using syslog Prevents the
sync before stopping, and does not log the halt using syslog Causes a quick halt, does not log the halt using syslog, and makes no attempt
to kill all processes Halts the system from a dial-up operation
EXAMPLES
To halt the system without logging the shutdown in the log file, enter: halt -l To halt the system quickly, enter: halt -q To halt the sys-
tem quickly, also leaving a crash dump for the savecore command, enter: halt -d -q To halt the system from a dial-up, enter: halt -y
FILES
Specifies the command path Specifies the syslog daemon Specifies the login accounting file
RELATED INFORMATION
Commands: fasthalt(8), reboot(8), savecore(8), shutdown(8), syslogd(8)
Functions: reboot(2), sync(2), syslog(3) delim off
halt(8)