The amber light (I think it's called System Attention) is switched on when anything hardware-related gets logged in the errlog. Check with "errpt -dH" to see what is there.
Note that by hardware-related it may not necessarily mean that something is broken. A power failure also gets logged in the...
The most common place to invoke skulker from is root's crontab. In your case it seems to be in /etc/inittab or possibly one of your /etc/rc* scripts.
We use skulker at my site but we have it run at midnight through cron:
0 0 * * * /usr/sbin/skulker >/var/adm/skulker.log 2>&1
1) Try sudo on IBM's Linux Toolbox CD. It's also available for download here
2) There's a technique to manipulate Korn Shell's SECONDS variable to use to for display the current time in the prompt here.
No, on the contrary, I would assume. With these routes AIX redirect packets destined to the same machine through the loopback interface instead of passing them down to the Ethernet device driver (or whatever type of card you have on your box) and I guess the reason for this is performance.
You need root-privilege to set a higher priority on a process. Use the setpri subroutine if you're writing a C-program or the command renice if you're writing a shell-script. setpri sets a fixed (only for the lifetime of the process) priority while renice just changes the nice value.
This may not be related to HACMP. If you're running AIX 5.x then this is normal behavior. The system redirects internal traffic to the loopback interface. Is 10.133.217.51 by any chance one of your interfaces on the machine?
Also:
1. Make sure that your RPC server on nodeA has bound to the right IP-address. Use rpcinfo -p ipaddress to see socket-number and then netstat -anf inet|grep socket.
2. You may need to delay the start of the RPC server on nodeA until after configuring the service-address. If this is an...
Another possible reason could be that the refresh rate is too high for the monitor. Try a lower rate. This can be changed with the command smitty chres_refrt.
The file /etc/nologin will disable all users except root. To allow more users to log in you could instead do this:
# chsec -f /etc/security/user -s default -a login=false -a rlogin=false
If you want to disable rsh and rexec logins as well:
# chsec -f /etc/security/user -s default -a...
I would not expect that moving the rootvg disks would work without problems.
Do you already have an AIX 5.2 running on the B80? If so then you could check what device drivers have been installed on it (lslpp -L "devices.*") and make sure the same are installed on the B50. Then take a mksysb...
How would you lock these accounts? At our site we have the standard practice of "disabling" the same accounts (and including some more). This we do with the command:
# chuser login=false rlogin=false ttys=ALL,!RSH,!REXEC shell=/bin/false username.
We also list the users in /etc/ftpusers.
All updates are cumulative. meaning that the highest level will also contain the updates from previous levels. To get bos.adt.samples up to 4.3.3.76 then you just apply that update.
Maybe it's this one?
3) AIX 5.2 : High impact/highly pervasive (2004.05.13)
APAR Number: IY56376
Systems with many devices may experience reboot loop where
system starts booting, displays 517 on LED display, and
then reboots.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.