Hi,
I had this same problem with a linux box in a Solaris environment (where
/home is the automounted home directory). I modified the spec file and rebuilt
the apache RPM to make it use a different home directory.
Venkatesh
>
> It is a bit strange for the first time.
> But is it a bit more complicated the next time... :)
>
> The question actually is about some packages.
> Just to remember, one of them is apache (that installs
> into /home/httpd). Another _was_ samba that used /home/samba
> for some strange purpose (samba doesn't need this, while
> apache does). I use nfs-mounted /home via automount for
> some machines, so that actual user's directories are shared,
> and user should not even notice it's phisical location.
> But if I install, e.g., apache, I will need to setup
> it's home directory on _different_ machine, so that apache
> will use files from nfs!? Yes, I know about symlinks, but
> this is not the case here. Or I should nfs-mount some other
> directory (not /home) and made symlinks like /home/$i => /mountpoint/$i
> for _ALL_ my users!?
> And, if /home/httpd does not exists on master machine, installing
> of apache will simply fail on non-master one...
>
> Maybe we should change all packages that touches /home/something to
> move things to, say, /var or /usr (should be considered for each
> package)? For apache this should be /var/httpd, I think...
> Yes, I know, this can break historic compatibility, but (again,
> as I think) a bit ugly one...
>
> So I recall -- what is the purpose of /home in RedHat Linux!?
>
> Regards,
> Michael.
>
> --
> To unsubscribe:
> mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
