similar to: Question on a long filename

Hi, I'm trying to convert a 33GB mail store from mbox to compressed mdbox (largest mbox is 2.7GB). The source store is live, e.g. there are mails delivered into it and mails are being read. Actually it is my own mail. :) Although my test runs were very successful I have run into trouble with the first run on the whole store. After fighting a bit around with errors like Error: Trying

Hi ? I do have replication between two servers running, and mail is replicated without any issues. I do have sieve running at both servers without any issues. But replication of sieve scripts doesn't work as "expected": Whenever I do modify my default script und upload it via "doveadm sieve put -u abc -a default < default" it becomes uploaded to the home directory of

> On 14.05.2015, at 19:21, Stephan Bosch <stephan at rename-it.nl> wrote: > > On 5/14/2015 2:46 PM, Michael Grimm wrote: >> Hi ? >> >> I do have replication between two servers running, and mail is replicated without any issues. >> I do have sieve running at both servers without any issues. >> >> But replication of sieve scripts doesn't

This is the rsync version I am using. rsync version 2.5.5 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal inums I have a file with a looooong name which I rsync from PC1 to PC2. (redhat-9) I am getting the

I'm not really what you would call a linux newbie, but I managed to run into a problem with rsync that has me stumped. I want to conduct un-attended backups of various files and directories over about 3000 miles of Internet, so I chose sshd and rsync for the job. I wrote a pair of scripts to do the job, the first to run incremental tars on the localhost, the second to run the rsync client.

https://bugzilla.samba.org/show_bug.cgi?id=11978 Bug ID: 11978 Summary: mkstemp failed: File name too long (36) when filename is under the limit Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

Hi, I've got a File name too long problem using rsync-2.5.6 or rsync 2.5.5-0.1 (debian) I had a look to the mailing list archive and to the todo file and all I've seen was that the problem only appears on old special systems. I'm using debian 2.2.20. (is it too old?) I've already posted this bug in debian bug tracking system

I have discovered that rsync 2.5.6 uses the mkstemp() routine wich do not have a 64bits version into the AIX libc. A very simple workaround to the big files writing rsync pb. is to not use this routine that create files w/ mkstemp() by modifying the "syscall.c" source file at line 154 as following : #if defined(HAVE_SECURE_MKSTEMP) && defined(HAVE_FCHMOD) become #if

Max Okumoto <okumoto@ucsd.edu> wrote: [CC changed to freebsd-security instead of the cvs list] We're talking about replacing the home-grown mkfifo() funktion in make (a modified copy of mkstemp()) with mkdtemp() and creating the fifo in this new directory. Max worries about a possible race with this new approach. > Its not a race between two nice programs :-) The function

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives:

This uses time, ASLR and pid for randomisation. (Closes: #516774) Signed-off-by: Thorsten Glaser <tg at mirbsd.org> --- usr/include/stdlib.h | 2 + usr/klibc/Kbuild | 2 +- usr/klibc/mkstemp.c | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 96 insertions(+), 1 deletions(-) create mode 100644 usr/klibc/mkstemp.c diff --git a/usr/include/stdlib.h

Hello, After upgrading to Samba 4.11 (from 4.10) I noticed that python scripts using tempfile.mkstemp fail when run against samba cifs mounts. Before I submit a bug report, could someone else try this out so it's not just my setup? How to reproduce: 1. Mount a Samba 4.11 share using the mount command: mount //server1/share /tmp/share1 2. Run python script that is using mkstemp: import

Hello all I have two Linux boxes. The first one is samba servers for the Windows clients. The second one is backup storage. So every few hours rsnc synchronises the data directories on the second machine. They are Suse Linux 9 Linux max 2.6.11.4-21.7-smp #1 SMP Thu Jun 2 14:23:14 UTC 2005 i686 i686 i386 GNU/Linux rsync version 2.6.3 protocol version 28 From time to time I get errors reported,

https://bugzilla.samba.org/show_bug.cgi?id=7670 Summary: rsync --hard-links fails where ditto succeeds Product: rsync Version: 3.1.0 Platform: Other OS/Version: Mac OS X Status: NEW Severity: blocker Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: Dave at Yost.com

Rsync reports the status code of the remote command. So in some situations the status code is successful when the command fails. Rsync of a remote file to a local read-only directory fails, but exits with $status = 0. I'd like to get $status = 23. Is it possible? Local copy fails with status = 23 > mkdir /tmp/nowrite > chmod -w /tmp/nowrite > rsync /etc/group /tmp/nowrite || echo

Pardon me if this is already known -- Theo, at least, had never heard of a Unix doing this. mkstemp() under Linux claims to conform to BSD4.3, but BSDs (FreeBSD and OpenBSD, at least) seem to have a slightly different behavior. Under Linux, new files are created with mode 0666, while under BSDs new files are created with mode 0600. A user need only set his umask to 0 and he will be able to