On Sat, 2006-02-25 at 11:26, Jean-Yves F. Barbier wrote: > No Craig, > > All machines automount the /NFS shares @ boot :( > > All machines have an existing /NFS mounted @ the backup time, > and only one includes it in its backupc. > > The only difference between machine I don't understand is the impossibility > to umount the /NFS/x on the problematic machine ("device is busy") and > I can't figure out why: I double checked that no console was in it and > no X program too.
"lsof" should show any open files below the mount point which would keep it busy. You can avoid the issue completely by adding --one-file-system to the tar or rsync arguments, then listing all the mount points that you do want to include in the ShareNames. You just have to be careful to include any additional filesytems you might add later. -- Les Mikesell [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/