similar to: DO NOT REPLY [Bug 6280] New: (Bug incl. PATCH) Linux mknod does not work when syncing fifos and sockets from Solaris

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

>Submitter-Id: current-users >Originator: Joao Carlos Mendes Luis >Organization: >Confidential: no >Synopsis: FreeBSD mknod refuses to create pipes and fifos >Severity: non-critical >Priority: low >Category: kern >Class: change-request >Release: FreeBSD 4.9-RC i386 >Environment: System: FreeBSD zeus.faperj.br 4.9-RC FreeBSD 4.9-RC #3: Sat Oct 25 17:54:52 BRST

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

https://bugzilla.samba.org/show_bug.cgi?id=8265 Summary: Long paths, hardlinks, 'special' files [was: Regression: sockets for 3.0.9pre1] Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: core AssignedTo:

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 ---

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

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 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

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

https://bugzilla.samba.org/show_bug.cgi?id=2868 ------- Additional Comments From rsync@cpe-24-95-91-210.columbus.res.rr.com 2005-07-23 23:36 ------- this should apply to both fifos and sockets. creation of both are unprivileged operations, see mkfifo(2), socket(2)/bind(2) on freebsd. suggest moving/modifying do_mknod in these sections backup.c generator.c to run regardles of uid and simply

When trying to move my root to a btrfs filesystem, I found a missing feature (or a bug). It's not possible to create device files. To reproduce, run this on a btrfs filesystem: mknod test c 1 1 result: mknod: `test': Operation not permitted Frank

The following patch (adapted to rsync 2.5.5 from the one posted in Dec. 2000, http://lists.samba.org/pipermail/rsync/2000-December/003349.html) is necessary to prevent rsync from failing on creating FIFOs or UNIX sockets on FreeBSD. Any chance for it to be integrated in a future release of rsync? Thomas. diff -ur work/rsync-2.5.5/config.h.in work.patch/rsync-2.5.5/config.h.in ---

I want * to answer the phone when call comes-in. I've enabled /dev/phone0 in phone.conf and created /dev/phone0 with a command: mknod /dev/phone0 c 100 0 Though, when I start * I get: Parsing '/etc/asterisk/phone.conf': Found Sep 12 00:18:42 WARNING[16384]: chan_phone.c:950 mkif: Unable to open '/dev/phone0' Sep 12 00:18:42 ERROR[16384]: chan_phone.c:1141 load_module: Unable

I have been running rsync for about 2 weeks now and I will occasionally recieve the following errors: mknod ./{filename} : Invalid argument mknod ./{filename} : Invalid argument mknod ./{filename} : Invalid argument mknod ./{filename} : Invalid argument mknod ./{filename} : Invalid argument wrote 16 bytes read 336751 bytes 131.52 bytes/sec total size is 33812275937 speedup is 100402.58 rsync

Show usage instead of segfaulting when no args are passed. 0d844078 added typec and assigned value without actually using it. As variable is properly named just use it in coressponding switch. Signed-off-by: maximilian attems <max at stro.at> --- usr/utils/mknod.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/usr/utils/mknod.c b/usr/utils/mknod.c index

Hi there, I already asked the list about the problems with sockets on FreeBSD (see here: http://www.mail-archive.com/rsync@lists.samba.org/msg08121.html). I adopted Andrew Flury's patch to the recent CVS version of rsync: Index: rsync.h =================================================================== RCS file: /cvsroot/rsync/rsync.h,v retrieving revision 1.155 diff -r1.155 rsync.h

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

Folks, I'm setting up to sync files from a staging env to a prodution env, such that the filesystems for both are served via nfs to their respective systems. Thus, I can do the rsync on the nfs server as a 'advanced cp'. rsnyc $parms filessystem filesystem2 Due to ownerships and permissions, I have to run this as root, but, I'd like the files to belong to another user and

Hi. rsync 3.0.8 FreeBSD RELENG_4 i386. rsync -Haxi --delete /.../ /.../ The first pathspec above (residing on zz, a full filesystem) is: /vvvv/wwww/xxxx/zz/ The second pathspec above (residing on yyy, an empty filesystem) is: /vvvv/wwww/xxxx/yyy/zz/ It's obviously a 'copy everything over' operation. I've had to obfuscate the pathnames, however the exact pathlength throughout

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