similar to: date of new directories

I am trying to use rsync 2.4.6 to try creating a backup using another locally connected hard disk. Thing copy, but sometimes the group is eith numeric (valid). Often the owner is not even shown. This is the command I use for rsync: rsync-2.4.6/rsync -arxlHpogDt /usr/ /backup/usr/ --delete I login as root. Any help would be appreciated. -- Ian Kettleborough ian@idk.com

Greetings! I'm experiencing these problems as described in this mail: ------- From: Thomas Quinot (thomas@melusine.cuivre.fr.eu.org) Subject: Rsync 2.5.5: FreeBSD mknod can't create FIFO's This is the only article in this thread View: Original Format Newsgroups: mailing.unix.rsync Date: 2002-06-24 06:05:25 PST The following patch

I was planning to use rsync to backup to a second drive, but I ran out of swap space. No problem, I will let rsync do it a few directories at a time overnight when the computer usually sits idle except for incomming email. I have 2 question: 1. How much memory does each file to be copied need. Obvisiouly I have too many files. 2. Why does this command work: rsync -ax /usr/xx /backup/usr/

Currently I only have one machine backing up to another. I am backing up to a filesystem that is mounted as nosuid. The syncing process works perfectly except it fails on files that are suid. Example proc/ root/ tmp/ mknod tmp/mysql.sock : Invalid argument mknod tmp/orbit-daud/orb-12573780511489051058 : Invalid argument mknod tmp/orbit-daud/orb-139425434385535813 : Invalid argument mknod

https://bugzilla.samba.org/show_bug.cgi?id=6280 Summary: (Bug incl. PATCH) Linux mknod does not work when syncing fifos and sockets from Solaris Product: rsync Version: 3.0.6 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Hi I am a rsync (on Mac OS X, RsyncX version with extended HFS+/-eahfs forks) beginner (I merely use it for backing up my desktop machine to a bootable external firewire volume, so that I can resume work in case of a harddrive disaster) and I got these messages: mknod "/Volumes/backup/Applications/Plone2/Sites/Default/var/zopectlsock" failed: Invalid argument mknod

Hi all, I am having problems to get the SeaLevel IO card to work with CentOS distro. Basically the card is being recognised and shown by lspci BUT /proc/devices file is not updated with the new devices does anyone know why. ? Could someone tell me what/where infos are needed to get /proc/devices to be updated. The reason I require the /proc/devices infos is because I want to run a mknod

Hi all, Currently, umask takes effect when we create device file via mknod, as bellow commands show: ><fs> mknod-b 0760 8 1 /dev/sdf ><fs> ll /dev/sdf brwxr----- 1 root root 8, 1 Apr 15 11:10 /sysroot/dev/sdf But I wonder whether it is reasonable? For mknod(1), when we use option -m mode, we set file permission bits to MODE, not a=rw - umask. Should this also be applicable

Hi All, I am trying to run rsync from HP11.00 machine (source) to HP11.11 machine, as test for migration plan. The data on the source is not changing since it is snapshot of active data. Every time we try to run the following command: timex rsync -avuz --delete isynh09:/snap We get the following error: receiving file list ... done mknod

Hello from ealier 6.0 there is problem with synproxy in pf filter: this one 6.1-PRERELEASE #2: Wed Mar 15 02:02:37 MSK 2006 pf.conf just with single rule pass in quick on lo0 proto tcp from any to any port 22 flags S/SA synproxy state result telnet 127.0.0.1 22 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. and it's hangs pfctl -s rules -v No ALTQ support in

I am trying to exclude a few directories from being copied to a 2nd local hard disk. I have read the doc's, used the --exclude-from= to specify the filename.. but What confuses me is whether a directory listed in this file should have a trailing / on it or is the file completely different fro what I think it is. ie: /usr/src or /usr/src/ Thanks Ian

I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good after upgrade until reboot. When rebooted to container I'm getting the following errors.. Any help would be greatly appreciated /bin/mknod: `/dev/lp2': Operation not permitted /bin/chown: cannot access `/dev/lp2': No such file or directory /bin/mknod: `/dev/lp3': Operation not permitted /bin/chown: cannot

Local end (receiving): 3.0.2, 3.0.3pre2 Remote end (sending): 2.6.9 Under 3.0.x, rsync sometimes prints an "Invalid argument" error when moving sockets to the backup directory (--backup-dir): rsync: mknod "/backup/machine/../machine-before-4/var/run/audit_events" failed: Invalid argument (22) The problem appears to be that, at least with sockets, keep_backup() is calling

Hello, My Cisco phone has software: Boot Load: PC030300 Ver: 3.2(7.0) And I want to upgrade it to SIP 6.0 Is it possible or I have to upgrade to ealier then 6.0 and then to 6.0 ? bart -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20031121/7331dff5/attachment.htm

Hi all, I ran across a few threads on google regarding FreeBSD's rsync mknod problem but I didn't find any good fix. I was wondering if anyone knows more about this and a good fix. Here's an example of the output. mknod qmail/queue/lock/trigger : Invalid argument mknod qmail/supervise/qmail-send/log/supervise/control : Invalid argument mknod

https://bugzilla.samba.org/show_bug.cgi?id=1804 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From wayned@samba.org 2004-09-22 09:56

Hi, I am wanting to use NUT to connect to an Eaton Powerware 5110 UPS using USB to connect. - I am using NUT 2.0.2 - I have compiled it with USB support - I can see that the UPS is registered as connecting in /var/log/messages eg usb 3-1: USB disconnect, address 3 usb 3-2: new low speed USB device using uhci_hcd and address 4 But I don't know how to progress from here.

Hi there, there is a problem (which as far as i know) is already known with rsync on FreeBSD: it is not possible to rsync neither fifos nor unix domain sockets (note that you have to be root there): # mkfifo test # file test test: fifo (named pipe) # rsync -a test test2 mknod test2 : Invalid argument rsync error: some files could not be transferred (code 23) at main.c(620) # file /var/run/log

Since mkfifo, mknod_b, and mknod_c add the correct file type to the modes of the resulting file, make sure the specified mode contains only permissions bits. --- daemon/mknod.c | 15 +++++++++++++++ generator/actions.ml | 21 ++++++++++++++++++--- 2 files changed, 33 insertions(+), 3 deletions(-) diff --git a/daemon/mknod.c b/daemon/mknod.c index 7f71210..9af8701 100644 ---

We are using rsync to maintain a warm mirror of our boot disks. I just updated to rsync 2.6.0 and noticed that the rsync runs are now getting errors when copying sockets. The system is running Tru64 5.1A pk 4 on an AlphaServer 4100. Is this a bug? Is there some way to not copy sockets or should I find all of them and add them to the exclude file? rsync was built using a straight ./configure