Displaying 20 results from an estimated 5000 matches similar to: "[Bug 1804] FreeBSD's mknod can't create FIFOs and sockets"
2009 Apr 20
6
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=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:
2003 Sep 15
1
rsyncing fifos and sockets on FreeBSD
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
2015 Jan 15
1
[PATCH] mknod: filter modes in mkfifo, mknod_b, mknod_c (RHBZ#1182463).
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
---
2002 Jun 24
0
Rsync 2.5.5: FreeBSD mknod can't create FIFO's
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
---
2003 Nov 30
0
FreeBSD mknod refuses to create pipes and fifos
>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
2005 Jul 24
2
[Bug 2868] Allow fifos to be copied by normal users
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
2002 Mar 22
2
Bug in compile of rsync 2.5.4 on Tru64 UNIX V5.1a using cc
Greetings, here is the output of the 'configure' step and
the compile step (using the Compaq cc compiler that comes
with Tru64 V5.1A. The configure reported success and most of
the compile steps cam through error/warning free except for
the one that stumbled. Can someone help me out here? I am willing
to provide a binary for Tru64 V5.1A if we can swat this bug.
We depend greatly on Rsync
2003 Dec 18
1
FreeBSD mknod errors
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
2010 Apr 15
2
Should umask takes effect when we create device file via 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
2005 Feb 09
1
rsync backups on Mac OS X - mknod errors + icon disappears...
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
2003 Aug 23
1
mknod / rsync error
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
2002 Apr 09
3
getaddrinfo.c error compiling rsync on tru64 5.1A
i've applied albert chin's patch on configure.in file:
http://lists.samba.org/pipermail/rsync/2002-January/005726.html,
but i still getting the error:
cc: Error: lib/getaddrinfo.c, line 180: In this statement, "EAI_MAX" is not
declared. (undeclared)
thanks for any advice
Martin Sigilfredo
_________________________________________________________________
Join the world’s
2007 Jun 29
2
Mknod: Operation not permitted
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
2011 Nov 25
1
Pipes (fifos) not working in concurrently
Hello
I have a large list of URLs (from a database, generated automatically
during tests) that I want to download using several wget processes at
the same time. With our internal web servers, this will be a lot faster
than downloading the pages one at a time with a single process.
So I create 20 pipes in my script with `mkfifo? and connect the read end
of each one to a new wget process for
2002 Jan 25
3
suid files and bsd
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
2004 Sep 11
1
mknod /dev/phone0 c 100 0
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
2010 Aug 17
6
DO NOT REPLY [Bug 7625] New: "Don't know how to make ./*.c"
https://bugzilla.samba.org/show_bug.cgi?id=7625
Summary: "Don't know how to make ./*.c"
Product: rsync
Version: 3.0.7
Platform: s390
OS/Version: Other
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned at samba.org
ReportedBy: sebastian.hoffman at
2003 Oct 27
0
rsyncing fifos and sockets on FreeBSD
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
2003 Feb 02
2
Encoding from fifo's
Hello, I'm new to the list, so if this is an FAQ, please point me to the
relevant docs.
I'm playing with Theora, to see what kind of quality I can expect (I
realise its not for production use yet). I've download the source from
CVS, and got it to build, with the example encoder and player.
While trying to find something to serve as a good source of input, I
decided I'd use a
2002 Mar 14
0
rsync 2.5.2 doens't compile on Tru64 5.1 and FIFO, socket files
Hi all,
I have rsync 2.5.1 (with a patch from albert chin - china@thewrittenword.com)
installed OK on Tru64 5.1 UNIX.
When I run rsync, it doesn't work with special files (FIFO, socket,...)
Here is the error:
mknod cluster/members/member1/dev/binlogdmb : Invalid argument
mknod cluster/members/member1/dev/log : Invalid argument
mknod cluster/members/member1/dev/printer : Invalid