Problem
Once a week, mail from cron called a "Verify Report" tells me I have broken or missing symbolic links on my system, listing the "problem" files.
Cause
At 04:00 A.M. every Sunday, cron runs (from the root user's crontab):
/etc/custom -V symlinksThis checks all the symbolic links in the Software Storage
Object (SSO) hierarchy. If there are any discrepancies
found, you are sent e-mail from cron containing the output
from the above. An example follows:Verify Report - Broken/missing symbolic linksDate : Sun May 07 04:03:47 GMT 1995
User : root
Machine : spamsco.london.sco.COMFiles With Discrepancies: 3
Total Discrepancies : 3Software selected for verification:All software on systemThe following expected symbolic links are broken or missing:
/etc/group->
/var/opt/K/SCO/Unix/5.0.0Cl/etc/group/etc/passwd->
/var/opt/K/SCO/Unix/5.0.0Cl/etc/passwd/etc/shadow->
/var/opt/K/SCO/Unix/5.0.0Cl/etc/shadow Solution
In most cases, these broken symbolic links should not prevent the system from working (as long as the files that have replaced the symbolic link are not missing or corrupt).
If you make changes to the users or groups on the system, these files may appear in the report:
/etc/group
/etc/passwd
/etc/shadow
/tcb/auth/files/*This is a known issue with SCO OpenServer 5.0.0 that is scheduled to be resolved in a future release.
Possible causes of other files appearing in this list are:
1. A system file has been removed or renamed.
2. A system file has been removed/renamed and restored.
3. 3rd party software has been installed that has modified a system file (by removing/renaming and then restoring it) thus breaking the symbolic link.
Note: If you want to restore the symbolic links:
(a) For links that pointed to files in /var:
These can be restored with custom(ADM)'s -x option, or by
using custom(ADM) interactively (use the "Software->Verify
System" menus). This is because the files in /var are
system data files (also known as "client" files) that can
change. An example of a client file is /etc/passwd.When custom(ADM) restores a symbolic link to /var, it:
1. Backs up the original version of the file under /var (to "/<var path>/<filename>#");
2. Copies the modified versions of the file into /var;
3. Restores the link to the new file in /var.
This means that when you restore the symbolic link to a data file, the file is not lost but moved to /var.
(b) For links that pointed to files in /opt:
Investigate why these files have changed. Then consider
carefully before restoring the symbolic link (either by
hand, via custom(ADM)'s -x option or by using custom(ADM)
interactively).This is because the files in /opt should not normally change
(these are also known as "shared" files) unless via a patch
or an upgrade. An example of a shared file is /bin/ls.When custom(ADM) restores a symbolic link to /opt, it:
1. Backs up the current version of the file (to "<filename>#");
2. Restores the link to the original file in /opt.
The above implies that any new functionality that the new file added will be lost by restoring the symbolic link, although you can recover it by putting the saved file back.
See also
custom(ADM)