Date: Thu, 7 Oct 2004 09:55:37 -0500 From: Kirk Strauser <kirk@strauser.com> To: freebsd-current@freebsd.org Subject: Re: Weird errors with gtar on 5.3-BETA7 Message-ID: <200410070955.40350.kirk@strauser.com> In-Reply-To: <1097105028.775.22.camel@prophecy.dyndns.org> References: <200410061755.42069.kirk@strauser.com> <1097105028.775.22.camel@prophecy.dyndns.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Wednesday 06 October 2004 18:23, Christopher Nehren wrote: > It means that you're trying to archive a file system which isn't > actually a file system -- in this case, /proc. You can use gtar's -X > option to exclude /proc and other non-file system paths from your > archiving. But shouldn't the "--one-file-system" option stop it from attempting to recurse into a mountpoint in the first place? bsdtar seems to handle that situation as expected: # gtar --one-file-system -cf /dev/null / gtar: Removing leading `/' from member names gtar: /proc: Cannot savedir: Invalid argument gtar: Error exit delayed from previous errors # tar --one-file-system -cf /dev/null / tar: Removing leading '/' from member names > You don't happen to be using procfs on a 5.x system, do you? procfs is > notoriously insecure (and, in my opinion, its very functionality is > insecure -- you shouldn't be able to see anything about anyone else's > processes. Period.). If you are using it, why do you need it? My "jailadmin" program uses /proc to get information about running processes. I haven't reworked that functionality yet. -- Kirk Strauser [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iD8DBQBBZVjs5sRg+Y0CpvERAlEPAJ9lNeD5THva3H4+GMMmQ6m5IJML6ACeISFy QC3iwBLxZwkdLHUCT+mocaw= =e4T8 -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410070955.40350.kirk>