Very Computer

Hello,

I'm fighting with a FreeBSD machine. Roughly what I'm up to: I clean
installed FreeBSD, with the DES option. The goal is to set up an Apache
on the machine. Then I performed a rdist from a BSDI machine, importing
stuff like password file, user directories, user quotas, shells. The
Apache works
just fine, but when I try to run Perl I get stuck with the error
message:
"Too many symbolic links" (under bash), "Symbolic link loop" (under sh).
I've
scanned through my symbolic links w/o finding something striking.
Basically, the
links I have are "shortcuts to shells", some links to user logs...
Anyone seen this kind of problem? Anyone solved it? How?

        Cheers

                Michael
--
Michael Hallgren, Easynet France
Write : http://www.loria.fr/tex
Play : http://www.perl.com/perl

Daring to challenge the will of the almighty Leviam00se, Michael Hallgren

: Hello,

: I'm fighting with a FreeBSD machine. Roughly what I'm up to: I clean
: installed FreeBSD, with the DES option. The goal is to set up an Apache
: on the machine. Then I performed a rdist from a BSDI machine, importing
: stuff like password file, user directories, user quotas, shells.

"rdist from BSDI?" Well, at the very least, the shells may well not work:
while FreeBSD (depending on the version) can run many BSDI binaries, you
might find some that don't work. You should not copy shell binaries from
a BSDI machine to a FreeBSD machine: you should install the native FreeBSD
versions instead. Tcsh, bash, pdksh and probably many others are in the
FreeBSD ports/packages collection. Alternatively, you can just get the
original source and build them yourself.

I might suggest using NFS to mount the user directories from the BSDI
host, except that I don't know if quotas will work. For the password
database, you should copy only the entries for your users from
/etc/master.passwd and use pwd_mkdb to make a new FreeBSD password
database (in other words, don't overlay the FreeBSD /etc/master.passwd
with the one from BSDI: just copy the entries for the users on your
system.)

: The
: Apache works
: just fine, but when I try to run Perl I get stuck with the error
: message:
: "Too many symbolic links" (under bash), "Symbolic link loop" (under sh).
: I've
: scanned through my symbolic links w/o finding something striking.

Evidently you need to be struck harder. :)

: Basically, the
: links I have are "shortcuts to shells", some links to user logs...
: Anyone seen this kind of problem? Anyone solved it? How?

Perl is also available for FreeBSD. That said, this error usually
indicates a circular link, i.e. a symlink that points to itself (or
one link that points to a second link, which in turn points back to
the first link).

Probably you don't really have a perl executable at all: you just have
a perl link that points back to itself. Install perl from the FreeBSD
packages collection and test it to make sure it works.

-Bill

--
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager, Master of Unix-Fu


=============================================================================
  "Now, that's "Open" as used in the sentence "Open your wallet", right?"
=============================================================================

Hello, again,

Don't think I'm crazy ;-)

I've solved my "Too many..." problem. Perl now works just fine :-).
But, (at least) two utilities doesn't want to work:

/usr/sbin/adduser and /usr/sbin/rmuser

My system claims that the files doesn't exist, but ls -l shows their
presense .

Well... ;-)

        Cheers

                Michael

Hi,

CU
        Sec
--
Fuer die Raupe ist es das Ende der Welt,
Fuer den Rest der Welt ist es ein Schmetterling
                                                            Error 0: No error

Thanks all of you. My problems are now solved. Nevertheless, I've got
one
more question:

I run virtual Web's, under Apoache. I'm starting Apache using a script
/usr/local/etc/rc.d/15httpd.sh. I want to start virtual IP interfaces
automatically. I try /usr/local/etc/rc.d/10vhost.sh --- 10 to make it
run
before 15httpd.sh. But it doesn't work. After reboot, if I run
10vhost.sh
manually, everything's working just fine.

Got a clue?

        Cheers

                Michael

Anyway, virtual hosts are meanwhile covered by the generic system
startup procedures.  You aren't mentioning your FreeBSD version, but
if it's 2.2 or higher, you should be able to do this with the standard
files.

--
cheers, J"org

Never trust an operating system you don't have sources for. ;-)