Kern Sibbald wrote: > Not only is it more complicated, but it can be very expensive. Suppose you > are restoring a million hard linked files. That could mean that you need > you will need to keep a list that could amount to hundreds of millions of > bytes (you need to keep at least forward links, the full path and the file, > as well as certain of the file attributes). If you are restoring 5 or 10 > million files, it could even be worse. In addition, if you have multiple > files linked together (i.e. more than 2), it would add more complication > because when hitting the second linked file in the list, the real file would > already be marked immutable. You can solve that by having a doubly linked > list in binary order, but then the computation costs go way up.
Why not just keep a list of filenames which should have the IMMUTABLE flag, and apply this flag after the whole backup is done to those files. > Off hand, I would say that the FreeBSD guys have worked themselves into a big > hole. They have violated the rule that says that root can do anything. root can by removing the schg flag first, assuming that the right securelevel is in place. -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
