Search results for query: *

If you are not using an HMC, the setting for the serial ports can be found by using a tty session into the HMC interface, you can also set your client NIC to the IP of the HMC port (found in the 520 docs) and use a browser to modify these settings.

Do you want to monitor size or writes? If you want to monitor the % full, that can be done with WSM not to mention a bunch of other scripts out there. I guess if you want to monitor file writes, you could modify one of those scripts to e-mail you everytime the free space drops ...

MIMS is a workforce managment app produced by mincom.

No resolution yet ...

Read the nmon guide. It will tell you how to script data collection for certain resources. It then puts the data in a form that the nmon analyzer will read into Excel and graph everything out for you.

You can perform a "local" install of the Peoplesoft application on each of the remote user's PCs. It's a pain for managing updates, but we've done it here with no problem. Simply copy the top level folder to the user's C: drive and update their shortcuts.

If you have two NICs that are on the same network segment (i.e. en0 = 135.100.50.1 and en1 = 135.100.50.2) and you want trafic to the 135.100.x.x network to default through en1: run an rmdev -dl on both en0 and en1 rmdev -dl en0 rmdev -dl en1 run config manager cfgmgr setup en1 FIRST...

I've seen Exchange authentication issues over VPN unless there is a BDC at the remote site. Any suggestions on getting around the BDC solution?

Well, we can bash in our profiles because bash is installed on /usr/local/bin that has, for various reasons, become an NFS mount accross all nodes. If NFS goes down and I need to get in to trouble shoot, I won't get a shell prompt.

I've narrowed the problem down to my .profile. The last line calls bash, and half the time it works the other half it doesn't. My PATH includes the directory where bash resides and once logged it, I can run bash from the command line. Very odd indeed. For now I've taken bash out of my .profile...

I have the same problem. It's just my account and it occurs from any machine on our network or on the console itself. Failsafe works fine, but the regular login process hangs infinatly.

You shouldn't have to do anything. In fact to test that, add an entry to the hosts file that reads: 127.0.0.1 localtest # This is an entry to test my hosts file

Very strange indeed....this is a stretch, but in your paste of the /etc/hosts info, there appear to be 2 or 3 spaces between loopback and localhost, can you verify? There should only be one space, but I don't think the hosts file really cares.

What happens when you ping 'loopback' instead of 'localhost'?

I think he is saying that it is not returning 127.0.0.1, but instead it is returning an IP from the other side of his gateway. But a ping of 127.0.0.1 returns OK.

Can you post the contents your /etc/hosts file? Seems as if there is an entry in there that has been messed up.