Hi again,

Im not having a very good day today! :)

Right well I just tried making a new VS and then realised that there
were no httpd process on it.  I went in manually and did...

bevs -r newvs
su web
/usr/sbin/httpd

and got
"Illegal Instruction".

Now I had a problem like this with the PHP module that comes with the
default skel but I replaced libphp4.so with a better version from Nigel
Marett and it had worked. So I commented out the PHP module lines and
everything works.  Hang on I thought - I replaced the libphp4.so with
the new version and everything worked - why am I getting this
again?...and then I remembered!

A while back I accidently mucked up the skel by doing a "bevs -r (vs)"
and changing ownership etc of skel files.  To repair my mess I did the
following....

Extracted the original skel file (.tar.bz) over the top of the old skel.
Then I commented out the check in vsd-linkvs.pl that checked whether you
were linking a VS to a skel it was already linked to.  Then I did
vsd-linkvs.pl and linked all my VSs to the skel again.

So this must be the problem - its using the old libphp4.so that I forgot
to update when I re-extracted the skel.  But what puzzles me is this...

I though the whole point of a skel is that files are hard linked in?  So
why are my other VSs still working now - if libphp4.so was overwritten
in the skel with a bad version - why are only new VSs affected?  To add
to the confusion I have just done an "ls -la" in "/usr/lib/apache" on
the newvs and see that the inode count of libphp4.so is only 2 whilst
all the other modules have an 8!?

Perhaps someone could clear up this confusion - what files in the skel
are copied to a VS and which are hard linked?

Thanks in advance - sorry about the email length!

Ben K
[EMAIL PROTECTED]


------------------------- The freeVSD Support List --------------------------
Subscribe:   mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
Archives:    http://freevsd.org/support/mail-archives/freevsd-support
-----------------------------------------------------------------------------

Reply via email to