SCO

1. Yes, but do it in single user mode. These files contain the data used by the 'who' and 'w' commands.

2. Is the root file system mounted? I know this sounds like an impossibility, but it is not.
Run divvy in order to list all the file systems on drive 0.
Run df -v and see if all file systems are accounted for.
In /etc/default run 'ls -li login' and see if the link to /var/opt/K still exists.

My belief is that the root file system has become corrupted as a result of running out of disk space.

Hi,
Please tell me how to run divvy for this?
Yes df -v show all filesystems:-
/ 33 (% Used)
/stand 55
/zlt 4
/back 4
/run 9
The 'ls li login' in /etc/defaults link exists for '/var/opt/K'.

I noticed that when i exec 'find / -name othman.rpt -print' as root I get screen-full of messages as in the Crout file ie 'var/opt/....../etc/default/filename does not exist. Surely this shouldn't happen??? Isn't this the problem as /usr/lib/cleantmp also does a find (not sure of other sys crons)? The cleantmp is run everyday at 3 3 but doesn't cause problems durring the week but maybe runs differently over week-end (due to file ageing I think)?? There are 0 size crout files everyday at 3 3 in /tmp.

This is very puzzling!!!
Thanks

'divvy' accesses the boot drive when used with no options.
Do not change anything, just note all the file systems and exit.

Run 'scoadmin', and choose 'software manager' then 'software' then 'verify system' then run once for each variation.

Run 'integrity -e' and correct permissions and ownership until there is no output.

1. Divvy output seems ok:

------------------+------------+--------+---+-------------+------------
| Name | Type | New FS | # | First Block | Last Block |
+-------------------+------------+--------+---+-------------+------------
| boot | EAFS | no | 0 | 0| 15359|
| swap | NON FS | no | 1 | 15360| 108543|
| root | HTFS | no | 2 | 108544| 1527928|
| zlt | HTFS | no | 3 | 1527940| 8867972|
| back | HTFS | no | 4 | 8867990| 16208022|
| run | HTFS | no | 5 | 16208050| 18305202|
| recover | NON FS | no | 6 | 1527929| 1527938|
| hd0a | WHOLE DISK | no | 7 | 0| 19550631|
+-------------------+------------+--------+---+-------------+------------
19542600 1K blocks for divisions, 8032 1K blocks reserved for the system

2. integrity -e has errors:

/var/opt/K/SCO/Unix/5.0.5Eb/etc/default/cleantmp (wildcard entry 79) is wrong.
Owner is root, should be bin.
Group is sys, should be bin.
Mode is 0664, should be 0644.
Type is FIFO (f), should be regular file (r).
/var/opt/K/SCO/Unix/5.0.5Eb/etc/default/codeset (wildcard entry 79) is wrong.
Owner is root, should be bin.
Group is root, should be bin.
/var/opt/K/SCO/Unix/5.0.5Eb/etc/default/cron (wildcard entry 79) is wrong.
Owner is root, should be bin.
Group is sys, should be bin.
Mode is 0755, should be 0644.
Type is directory (d), should be regular file (r)

I can change the owner, group & mode but not sure how to change filetype?
The actual files don't seem right. I did an ls of the folder (below) ie problem files & few others. Please note the dates, cleantmp is 0 size, cron is a folder. Should these be like this??

Not sure how this happened. Could manualy running 'cron' ie without any arguments the lastime cause this?? Whats the FIFO file in the /usr/lib/cron folder for? Seems like its regulary changing date/time but noted on solaris (localy Zimbabwe) in /etc/cron.d its static but we also run cron jobs here?

rw-r--r-- 1 bin bin 795 Mar 21 2000 Stp
-rw-r--r-- 1 bin bin 2336 Mar 21 2000 archive
-rw-r--r-- 1 bin bin 3629 Mar 21 2000 authsh
-rw-r--r-- 1 bin bin 631 Mar 21 2000 backup
-rw-r--r-- 1 bin bin 829 Mar 21 2000 boot
prw-r--r-- 1 bin bin 0 May 14 13:39 cleantmp
-rw-r--r-- 1 bin bin 4 Jun 4 08:04 codeset
drwxr-xr-x 2 root sys 512 May 4 13:24 cron
-rw-r--r-- 1 bin bin 2641 Mar 21 2000 device.tab
-rw-r--r-- 1 bin bin 617 Mar 21 2000 dumpdir
-rw-r--r-- 1 bin bin 1225 May 15 18:09 filesys
-rw-r--r-- 1 bin bin 649 Mar 21 2000 format
-rw-r--r-- 1 bin bin 984 Mar 21 2000 goodpw
-rw-r--r-- 1 bin bin 626 Mar 21 2000 idleout
-rw-r--r-- 1 bin bin 1228 Mar 21 2000 issue
-rw-r--r-- 1 bin bin 437 Mar 21 2000 lang

3. 'scoadmin, software manager' is comming with errors. Does it have to be done in suser mode?? I am accessing the server remotely using Radmin in Zambia & I am in Zimbabwe so its difficult to stop/start the server.

Thanks.

Lets answer the easy one first. You do not have to be in single user mode to run scoadmin, or any of its sub menus.

The four files that you highlighted in the list are all simple text files.
The filesys file would change if you had changed the file system mount points,
or had run mkdev fs (filesystems option in scoadmin).
The other files would likely not have changed since the original installation.

The FIFO file is normal in /usr/lib/cron.

For cleantmp, codeset, and cron, do you have a backup prior to May 29, that you can restore these files from.

-rw-r--r-- 1 bin bin 656 Sep 29 2000 cleantmp@
-rw-r--r-- 1 bin bin 1244 Sep 29 2000 codeset@
-rw-r--r-- 1 bin bin 915 Sep 29 2000 cron@
-rw-r--r-- 1 bin bin 1302 Mar 20 2003 filesys@

If you don't have a backup, send me an email, and I will forward them to you.
Filesys is probably correct, otherwise the non root file systems would not mount properly when the system is booted.
Codeset contains the default info for which character set is used.
Cleantmp contains a list of directories to be purged
Cron contains a list of log size defaults for cron

Hi jgt,

Unfortunately, I don't have a backup of the system.

Please advise how I can get your email addr; as your profile prevents me from emailing you.

Thanks.

Changed my profile to allow email.

Jack