16.05.2015 Views

Working with the Unix OS

Working with the Unix OS

Working with the Unix OS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Unix</strong> Administration<br />

New Software<br />

! Purchasing<br />

For major equipment & software purchases ask to see things working before you commit yourself. This includes<br />

hardware AND software.<br />

! Installing<br />

- Backup previous version of system<br />

- Installation may need root privileges. If shareware or network software – use source code from moderated<br />

news groups.<br />

- Keep software packages in separate directories to handle future releases.<br />

- Test basic features.<br />

- Check software works in non-privileged accounts.<br />

- Liaise <strong>with</strong> customer support from company supplying <strong>the</strong> software if problems occur.<br />

$ IS YOUR SYSTEM HUNG?<br />

A hung system is kernel resident <strong>with</strong> no kernel activity. Down and disabled system is kernel active but no results.<br />

A dead system <strong>the</strong> kernel has gone, processes are stopped.<br />

$ FILES THAT WOULDN'T DIE<br />

foo^H^H^Hbar, *, "- *", o<strong>the</strong>r assorted control sequences<br />

rm -i ?<br />

# confirmation for a single character file<br />

ls -ilb * # list strange file names<br />

od -xc # octal dump of parent directory<br />

clri<br />

# clear an inode<br />

/etc/unlink # or system call<br />

$ WON'T WORK<br />

Common problems that usually appear when a user complains "<strong>the</strong> system does not work properly".<br />

e.g. pr .profile | lp # no longer works<br />

The x bit has been removed for <strong>the</strong> owners home directory<br />

e.g.<br />

System administrator performs chmod 666 recursively from root, thus no traversal privileges - end of system.<br />

$ NO DISK SPACE<br />

df –t<br />

# show no disk free<br />

sed -n '$p' /usr/spool/console/May19 # print last line<br />

find / -type f -size +100000c –print # find large files<br />

(fuser -uk /dev/dsk/0s5; umount /dev/dsk/0s5)<br />

fsck /dev/dsk/0s5<br />

# no errors now<br />

The in-core inode table had been corrupted<br />

$ TERMINAL WON'T GET PAST LOGIN<br />

Warning some terminals have <strong>the</strong> ability to map characters. If in doubt reset back to factory defaults first.<br />

tset -m ansi:ansi -m tvi910:910 # BSD command<br />

echo AT > /dev/tty03<br />

# possible problem<br />

ls -l /dev/tty??<br />

# may reveal a nondevice<br />

remove it and make device knowing major and minor numbers<br />

mknod /dev/tty03 c 1 3<br />

# remake device<br />

199

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!