RE: NFS trys following remote symlinks as if local!
On Wed, 2001-11-21 at 04:10, Kelley, Tim (CBS-New Orleans) wrote:
>
> Can you overcome your problem by using relative links, e.g.
>
> #ls -l
> /usr/X11R6/lib/X11/kdm -> ../../../../etc/kde2/kdm
>
> instead of
>
> /usr/X11R6/lib/X11/kdm -> /etc/kde2/kdm
>
>
> This is one reason relative style links are used and not absolute ones
Yes relative links are the solution to navigating an NFS mount. I'm
changing all my links to relative ones.
To overcome the inability of NFS to browse within remote mount points
I've just had to set up a more complicated exports file and mirror that
structure in the client side fstab.
Thanks also to Dave for the followups and the tip to use NIS if I don't
want to reproduce the client-side mounts in fstab.
Just a tip for everyone that I was looking for a cp-like local mirroring
tool (not a remote mirroring tool like rsync). Turns out it's logically
called cpbk:
apt-cache show cpbk
...
Description: a mirroring utility for backing up your files
Backup Copy is basically a smart copy program that allows a user to
copy mass files from one place to another. When coping over a
previous copy, the key features will allow coping only of new or non
existing files in the backup. This results in saving time and less
load on the drive. Built into the same feature of copying new files
only, is a file removal procedure. If a file is removed from the
source path, the same file will be removed when the next backup is
performed. This provides a backup that is exactly the same as the
source without filling up the drive. As an added option, all files
that will be overwritten or deleted when doing a copy over a previous
backup, have the opportunity to be stored in a trash bin. You can
leave this trash bin to grow and grow just in case you need a backup
of your backup. When you start running out of disk space you will
need to remove or clean up the trash bin.
Regards,
Adam
Reply to: