Displaying 20 results from an estimated 8000 matches similar to: "rsync backups on Mac OS X - mknod errors + icon disappears..."
2004 May 05
1
"Bad address" error
I'm getting a "bad address" error which is causing my rsync process to
bomb out.
I'm running RsyncX 2.1, in daemon mode on the source machine, with a
script to pull the information to the backup server. Both servers are
Xserves running OS X Server 10.2.8. Rsync target is on an Xserve RAID.
The RAID has 350GB free, so I'm not running into a disk full situation.
My command
2006 Aug 05
3
Newbie: What does -e do?
Hi
Just starting out, and have read through the man and several web page
tutorials, and I don?t quite understand some of the options (guess I?ll ask
about those as I get to them).
The first I see pretty often is ?e. Can someone explain what this does?
Thanks :)
All My Best,
Jeffrey
-------------- next part --------------
HTML attachment scrubbed and removed
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
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
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:
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
2004 Aug 12
1
link-dest doesn't seem to work properly on MacOSX
I have been trying to use rsyncx to generate a script for rotating backups
but it seems to me that the --link-dest option doesn't work properly in my
configuration. Instead of creating hard links for all unchanged files it
seems that rsync copies everything, as if --link-dest hasn't been
specificed. Can somebody clarify what's going on?
My script is ptovided below:
#rotating backup
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
---
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
2004 Sep 22
6
[Bug 1804] FreeBSD's mknod can't create FIFOs and sockets
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
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
2004 Nov 22
0
rsyncX hangs on Mac OS X
I am attempting to backup the Users directory on my desktop running OS
X 10.3.6. I am backing up to Jaguar Server 10.2.8. I am using RsyncX
version 2.1 on both systems. RsyncX Server is set up to run on both
systems however in this instance the Rsync client is my desktop and
server is Panther Server.
When I kick off an RsyncX session, RsyncX will run for a while, then
stop part of the way
2004 Mar 22
3
Rsync killed my server
I have the following as a line in a script kicked off from cron:
sudo rsync -e ssh -avz /Times_QPS/ 192.168.22.72:/Times_QPS/ --eahfs
It logs the output to a log file, however rsync caused the log file to go to an 80gb file and fill up my disk because it threw a mental when a file it went to sync was no longer there!
Is there some way to get the sync to ignore errors?
-Jason
2002 Aug 26
0
rsync error: mknod, invalid argument
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
2010 Nov 10
0
[PATCH] utils: mknod massage
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
2006 Aug 07
1
chown errors?
> Hi--
>
> I just tried my first rsync operation. I got a couple of errors I don?t
> understand. Could someone explain what might be happening here?
>
> Please know that I am working in rsync for Mac OS 10.4, which includes a few
> odd options discussed in previous posts.
>
> The original command was:
>
> time rsync -a -v -e ssh /'Applications'
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
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
---
2019 Sep 24
2
Can't Get SASL to Work
I have been fighting with this for almost 2 days. I can't seem to get the
SMTP server to authenticate through SASL. I have turned so many things off
and on, I don't remember what I've done, anymore. Can someone look at these
and tell me what I'm missing. I get this in the log, anytime postfix tries
to authenticate.
Sep 24 19:48:14 ubuntu postfix/smtpd[14464]: warning: SASL:
2005 Jan 13
1
Digital IO card and /proc/devices
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