- Never do something you can't undo.
- Always check the backups, never assume they are working. Make sure you can restore from them, too.
- Write down what you did, even if you know you will never forget it, you will.
- If you do it more than once, write a script.
- Get to know your users before there is a problem, then when there is, they will know who you are and maybe have a little understanding.
- Remember you are performing a service for your users, you don't own the system, you just get to play with it.
- Check your backups.
- Never stop learning, there is always something you should know to make your job easier and your system more stable and secure.
- Check your backups, again.
When network service like telnet connection hangs, then it is possible the inetd subsystem is not working properly. # refresh -s inetd 0513-095 The request for subsystem refresh was completed successfully. If the refresh hangs for some time and comes back with 0513-056 time out waiting for command response, then the inetd subsystem may not be working correctly and should then be killed nicely. Run #ps -ef | grep inetd and do a kill -15 on the process ID on the line that has /usr/sbin/inetd. Once inetd has been killed, type startsrc -s inetd. If inetd starts, try to telnet into the machine. If inetd does not start up successfully, or if telnet still hangs indefinitely, run kill -15 on the PID of inetd again. Back up the original /etc/inetd.conf file to a new file name by typing: # mv /etc/inetd.conf /etc/inetd.conf.backup The original template is in /usr/lpp/bos.net/inst_root/etc/. You can copy it by typing: # cp /usr/lpp/bos.net/inst_root/etc/inetd.conf /etc/inetd.conf Run start...
Comments
Post a Comment