Technical article 109217

Emergency floppy creation fails with the error message "exec: Too many symbolic links in path" when using SCO ARCserve/Open Release 2.2.0k.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

After installing or upgrading to SCO ARCserve/Open Release 2.2.0k,
it is not possible to create emergency floppies using the 'mkarcboot'
program.  Any attempt to create the floppies will result in the
error:

exec: Too many symbolic links in path.

Cause

When the new release of SCO ARCserve/Open was put on the Optional
Services CD-ROM, the directory /usr/lib/arcboot was exported as a
directory and a symlink.  When the mkarcboot utility is run, this
creates a situation where the symlink points to the directory that
points to the symlink, and a circular path is created resulting in
too many symbolic links.

Solution

This will be corrected in the next release of SCO ARCserve/Open.
Until that release is available, the enclosed shell script can be
run to correct the problem on existing installations.  The following
steps outline this procedure:

1. Log on to the system as the root account.

2. Use a text editor to save the enclosed shell script.  The script
may be saved in any directory and may be given any name.  As an
example, save the file as "fix_arcboot.sh".
3. Modify the permissions on the saved shell script to include
execute permissions.  Use the command:
chmod +x filename

Using the example filename from step 2, the command would be:

chmod +x fix_arcboot.sh

4. Run the shell script from the command line using the syntax:

./path/filename

Using the example from step 2, the command would be:

./fix_arcboot.sh

5. The mkarcboot utility should now function and the floppies can be created.

=============================================================================
BEGIN CUT HERE
#!/bin/sh
# Fixes a packaging problem in the 2.2.0k arcboot package that causes
# users not to be able to generate disaster recovery disks.
#
# Problem is that the /usr/lib/arcboot directory was exported as a
# directory and as a symlink, which messed things up.  To fix this,
# we'll remove the bogus symlinks to the binaries in that directory
# (symlinked in from /opt/K/SCO/arcboot/2.2.0k/usr/lib/arcboot) and
# then remove the /usr/lib/arcboot symlink.  Then we create a
# standalone /usr/lib/arcboot directory and symlink in the proper
# files.  Lastly, we'll update the packaging file so that removal and
# installation verification will work correctly.
# SSO directory where the arcboot files are located
FIX_DIR=/opt/K/SCO/arcboot/2.2.0k/usr/lib/arcboot
# remove bad links from /usr/lib/arcboot (and also $FIX_DIR)
for idx in .arcfuncs .mkfuncs arcboot archd as_cmd as_badtrk as_recover ; do
    /bin/rm -f /usr/lib/arcboot/$idx
done
# remove symlink to $FIX_DIR
/bin/rm -f /usr/lib/arcboot
# restore original files in $FIX_DIR
for idx in .arcfuncs .mkfuncs arcboot archd as_cmd ; do
    /bin/mv  -f $FIX_DIR/$idx# $FIX_DIR/$idx
done
# create standalone /usr/lib/arcboot directory and set owner and
# privileges
mkdir -p /usr/lib/arcboot
chown root /usr/lib/arcboot
chgrp sys /usr/lib/arcboot
chmod 770 /usr/lib/arcboot
# create proper symlinks from SSO to /usr/lib/arcboot
for idx in .arcfuncs .mkfuncs arcboot archd as_cmd ; do
    /bin/ln -s $FIX_DIR/$idx /usr/lib/arcboot/$idx
done
/bin/ln -s $FIX_DIR/arcboot /usr/lib/arcboot/as_badtrk
/bin/ln -s $FIX_DIR/arcboot /usr/lib/arcboot/as_recover
# fix SSO file list so that software verification/removal work properly
cat > /opt/K/SCO/arcboot/2.2.0k/.softmgmt/ARCBOOT.fl << EOT
PKG SCO:arcboot:ARCBOOT
DIR 0770 root other - ./usr/lib/arcboot
FILE 0744 root other 1 256516 4086971314 - - - 0 0 ./usr/lib/arcboot/arcboot
EXPORT - ./usr/lib/arcboot/arcboot /usr/lib/arcboot/arcboot
EXPORT - ./usr/lib/arcboot/arcboot /usr/lib/arcboot/as_badtrk
EXPORT - ./usr/lib/arcboot/arcboot /usr/lib/arcboot/as_recover
FILE 0744 root other 1 12546 2957777209 - - - 0 0 ./usr/lib/arcboot/as_cmd
EXPORT - ./usr/lib/arcboot/as_cmd /usr/lib/arcboot/as_cmd
FILE 0744 root other 1 23540 563405794 - - - 0 0 ./usr/lib/arcboot/archd
EXPORT - ./usr/lib/arcboot/archd /usr/lib/arcboot/archd
FILE 0744 root other 1 12306 1998114349 - - - 0 0 ./usr/lib/arcboot/.arcfuncs
EXPORT - ./usr/lib/arcboot/.arcfuncs /usr/lib/arcboot/.arcfuncs
FILE 0744 root other 1 31977 3855673638 - - - 0 0 ./usr/lib/arcboot/.mkfuncs
EXPORT - ./usr/lib/arcboot/.mkfuncs /usr/lib/arcboot/.mkfuncs
FILE 0744 root other 1 42016 3374837998 - - - 0 0 ./usr/bin/mkarcboot
EXPORT - ./usr/bin/mkarcboot /usr/bin/mkarcboot
FILE 0744 root other 1 1213 2334533606 - - - 0 0 ./usr/lib/terminfo/a/arcansi
EXPORT - ./usr/lib/terminfo/a/arcansi /usr/lib/terminfo/a/arcansi
DIR 0755 root other - ./usr/lib/arcboot/nls
DIR 0755 root other - ./usr/lib/arcboot/nls/C
EXPORT - ./usr/lib/arcboot/nls/C /usr/lib/nls/msg/C_C.C/arcboot
EXPORT - ./usr/lib/arcboot/nls/C /usr/lib/nls/msg/en/arcboot
EXPORT - ./usr/lib/arcboot/nls/C /usr/lib/nls/msg/english/arcboot
FILE 0744 root other 1 7391 18373363 - - - 0 0
./usr/lib/arcboot/nls/C/arcboot.cat
FILE 0744 root other 1 14351 4004114781 - - - 0 0
./usr/lib/arcboot/nls/C/arcshell.msg
EOT
exit 0
END CUT HERE
==============================================================================

From the Xinuos technical article database, record 109217. Reproduced with permission. The original is at www.sco.com/ta/109217, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.