similar to: mknod / rsync error

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

Hi list, Since upgrading rsync to version 2.5.2 on a Solaris 2.5.1 box, I see plenty of Warning: unexpected read size of 0 in map_ptr when doing my nightly backup (rsyncing some directories to an rsyncd on the same LAN). I have never seen this message before, and I only see it on the Solaris machine (I upgraded all my other machines to 2.5.2 as well). I hope this is not a FAQ... I did not find

When using rsync 2.5.2 as daemon on a Solaris 2.5.1 box, I cannot copy data to rsync volumes with option 'use chroot'; I get the following messages on the client: pipe failed in do_recv rsync error: error in socket IO (code 10) at main.c(375) rsync: connection unexpectedly closed (69 bytes read so far) What seems to occur on the server is that socketpair(3) (not pipe(2)) is called,

I have been trying to install 3.4p1 on a number of machines. Servers on ia64 Linux, i386 Linux and SPARC Solaris are all working like charms. On the other hand, I am having trouble at least with HPUX 11, DEC OSF 5.1 and Unixware: on all those systems, sshd bails out after authentication with an error in buffer_append_space. Here is the output of sshd -d on the UnixWare machine (uname -a:

Bonjour, I have some problem to configure a printing server with samba. I have a private network with a linux box as a gateway to the internet and several machine on this network some under windows, others under linux. One of the linux machine (which is not the gateway) has a printer which I want to be shared by the windows machines. The gateway has 192.168.0.1 as private IP number and the linux

* H. Peter Anvin, 2014-06-10 : > You probably want to test both pxelinux.0 and lpxelinux.0... if it is > sticking in pxe_init_isr you're using the latter. Correct. And indeed pxelinux.0 goes much further than lpxelinux.0! I have a few issues yet to fix: * Undef symbol FAIL: __syslinux_debug_enabled (I must have done something wrong while building) * find proper fix for

On Jun 10, 2014 4:47 PM, "Thomas Quinot" <syslinux at thomas.cuivre.fr.eu.org> wrote: > * find proper fix for serial i/o (my crude hack handles > output, but not input; I now end up with a boot: prompt > but cannot enter anything). Is there a known correct way > of setting up pxelinux for serial-only I/O? Did you see the SERIAL directive? If this

* Gene Cumm, 2014-06-10 : > Did you see the SERIAL directive? If this isn't enough, there may be bugs > in the modules or the libraries they use. Yes, I'm aware of SERIAL, my config file has: serial 0 19200 0 console 0 Thomas.

On Jun 10, 2014 4:59 PM, "Thomas Quinot" <syslinux at thomas.cuivre.fr.eu.org> wrote: > > * Gene Cumm, 2014-06-10 : > > > Did you see the SERIAL directive? If this isn't enough, there may be bugs > > in the modules or the libraries they use. > > Yes, I'm aware of SERIAL, my config file has: > > serial 0 19200 0 > console 0 > >

I've got a possibly silly question and I believe I have an answer, but I want to see if what I think is the answer is feasible. I've had to rebuild a mail server from scratch, upgrading from 4.6-STABLE to 4.8-STABLE in the process. The other mail server had crashed, with disk errors so sever it wouldn't fsck clean. I was able to get it together enough to pull my configuration files

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

>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

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

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

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

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:

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

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