Can't stat -t problem

mike wolman
Mon, 7 Jan 2002 20:04:44 +0000 (GMT)

Hi Ben,

I have checked and am pretty sure there are no dev files being backed up,
this is the command line i am using:

/usr/local/bin/rdiff-backup -v6 \
--exclude '/dev' \
--exclude '^/home/web/.*/access\.log' \
--exclude '^/home/web/.*/error\.log' \
--exclude '^/home/web/.*/www/log/' \
--exclude '/home/db' \
--exclude '/mnt' \
--exclude '/proc' \
--exclude '/tmp' \
--exclude '/usr/doc' \
--exclude '/usr/info' \
--exclude '/usr/man' \
--exclude '/usr/local/lib/mysql' \
--exclude '/usr/local/man' \
--exclude '/usr/tmp' \
--exclude '/var/catman' \
--exclude '/var/tmp' \
--exclude '/var/run' \
--exclude '/var/spool' \
--remote-schema "ssh -C %s 'sudo /usr/local/bin/rdiff-backup -s'" \
mike@remotehost::/ \

I will have an extra check to see if there are any other dev files about
but it is a plain webserver without anything special running.


On Mon, 7 Jan 2002 wrote:

> rdiff-backup usually uses python's os.lstat() function to stat files.
> However, probably for portability reasons, python's stat doesn't yield enough
> information to backup device files.  So if rdiff-backup is run on a device
> file, it will execute 'stat -t' to find the major/minor device numbers for
> the file, and then will run mknod to make the target file.
> If 'stat -t' doesn't work on the 6.2 box then rdiff-backup won't be able to
> backup dev files there either.  If it has worked so far it's probably because
> there are no dev files.
> I'm open to suggestions on better ways of dealing with dev files, because the
> 'stat -t'/mknod way isn't very portable.  But I've just assumed that the dev
> files live in /dev, so they are easy to exclude, and not very important to
> backup since most systems have a MAKEDEV file that recreates them.
> --
> Ben Escoto
> _______________________________________________
> Rdiff-backup mailing list
> Rdiff-backup@keywest.Stanford.EDU
> http://keywest.Stanford.EDU/mailman/listinfo/rdiff-backup