similar to: What happens after --max-delete is reached? Are updates processed?

Hi, I have a weird thing I don¹t understand. Here¹s what I did: I read some data: data=read.table("fileName²) then I printed the data to the screen: data But it didn¹t finish: lot¹s of data was written out, but not all of it... Then it interrupted and said: [ reached getOption("max.print") -- omitted 8178 rows ]] Is there a setting somewhere that I can change to get to see all of my

Dear useRs, does anyonw now how to avoid [ reached getOption("max.print") -- omitted 138 rows]. i read from the R forum that it can be avoided by increasing the 'max.print' option as much as i like, but i dnt know, how?? need your help on it. regards eliza [[alternative HTML version deleted]]

Is there any way to specify a file to be deleted on the remote side explicitly by name? I would have thought that deleting the file locally, the rsyncing the non-existing file with --del would have resulted in the remote file, which does exist being deleted. I have a general purpose script that my developers use to push updates from a devel box to all production boxes. It's essentially

https://bugzilla.samba.org/show_bug.cgi?id=2408 Summary: when more than --max-delete files are about to be deleted no error is returned Product: rsync Version: 2.6.3 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=2408 ------- Additional Comments From arthur@west.nl 2005-03-02 08:28 ------- Created an attachment (id=1003) --> (https://bugzilla.samba.org/attachment.cgi?id=1003&action=view) patch to limit the number of deletes before the deletes take place Ok, uploaded the patch as a file instead of the comment of the orriginal report. -- Configure

As part of coreutils' bootstrap, rsync crashes on cygwin: $ /usr/bin/rsync \ --delete \ --exclude '*.s1' \ -Lrtvz 'translationproject.org::tp/latest/coreutils/' \ 'po/.reference' rsync: failed to connect to translationproject.org (*inet_ntop failed*): Connection refused (111) Segmentation fault (core dumped) $ cat rsync.exe.stackdump

I use redis as quota backend (currently). After upgrading to 2.2.26.0 I see a ton of "Error: redis: Unexpected input (state=0): -ERR max number of clients reached" errors. It looks like either more Redis connections are being made, or Redis connections don't time out/are reused correctly anymore. No such errors were seen in 2.2.24. -- Tom

Is there a way to prevent rsync from deleting any files if --max-delete is exceeded? I want to avoid having my hourly cron job inadvertently destroy my backup a chunk at a time. By morning, the damage would already be done. Ideally, it should just stop and not sync or delete anything since something is horribly wrong. The only way I could see to do it is by running rsync twice - something

https://bugzilla.samba.org/show_bug.cgi?id=9427 Summary: Description of "--max-delete=" in manual page needs clarification Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

Processing commands for control@bugs.debian.org: > reassign 387238 xen-hypervisor-3.0.2-1-i386 Bug#387238: xen-hypervisor: Xen hypervisor reboots when scrubbing ram message is reached: confirmed on AMD64 and i386 Warning: Unknown package 'xen-hypervisor' Bug reassigned from package `xen-hypervisor' to `xen-hypervisor-3.0.2-1-i386'. > -- Stopping processing here. Please

Hi, When using --max-delete=NUM, NUM + 1 files get deleted. Test it by doing this: # mkdir src # mkdir dest # cd src # touch 1 2 3 4 5 # cd .. # rsync -avu src/ dest # cd src # rm 1 2 # cd .. ( Here i try to sync src and dest, but only delete one file from dest at the time. This would prevent an accidental rm in src from propagating to dest. ) # rsync --delete -avun --max-delete=1 src/ dest

I am using CALDERA OPENLINUX 3.1.1 with latest patches and Samba 2.2.5 on it. But recently I start to receive linux error "kernel: VFS MAX FILES REACHED" and Samba error "Too many open files". After it I tuning linux increase open files descriptors in /etc/security/limits.conf * soft nproc 4094 * hard nproc 16384 * soft

I am trying to encode the Sintel documentary AVI from DVD #3 using ffmpeg2theora 0.27 (which is the latest released version). You can download this AVI file from http://www.archive.org/download/Sintel/Sintel_Documentary_by_Ali_Boubred.avi I'm doing this encode on Fedora 13 GNU/Linux on a 64-bit AMD processor. The program encodes the video but I get something that looks like a warning and

I am having a problem with running utorrent on wine. After running for a little while I eventually get: Error: Too many files open. I have set ulimit -n unlimited which gives me: Code: root@???: 02:43 AM :~# ulimit -n 1048576 root@???: 02:43 AM :~# Also its got plenty of file descriptors so it doesn't seem like wine is truly using up to that amount: Code: root@???: 02:43 AM

On 11/06/19 13:29, Rowland penny via samba wrote: > On 11/06/2019 13:13, Sebastian Arcus via samba wrote: >> >> On 11/06/19 11:49, Rowland penny via samba wrote: >>> On 11/06/2019 11:38, Sebastian Arcus via samba wrote: >>>> >>>> On 11/06/19 11:07, Rowland penny via samba wrote: >>>>> On 11/06/2019 10:34, Sebastian Arcus via samba

Recently a gluster I setup got mounted on a server that exports it through samba. It appears to work till a point. Unexpectedly on heavy usage the nodes happen to reach the max file descriptors opened limit really easily. Anybody else has experience on it? Is that kind of usage supported. currently one node seems to have surpassed about 3M open files even if the samba server claims to have

Hi, With the current btrfs quota implementation, when you reach a subvolume quota limit, you can''t delete anything without first removing the limit or enlarge it: rm: cannot remove `testfile.bin'': Disk quota exceeded Is there any plan to change that? Thanks, Jerome -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

On 02/12/19 15:44, Rowland penny via samba wrote: > On 02/12/2019 15:32, Sebastian Arcus via samba wrote: >> >> On 02/12/19 15:10, Rowland penny via samba wrote: >> >> Thank you for the quick reply. I should have mentioned that these DC's >> are at at different sites. At each site there is only one Linux server >> - hence why the DC is also the file

On 02/12/19 16:53, Rowland penny via samba wrote: > On 02/12/2019 16:24, Sebastian Arcus via samba wrote: >> </snip> > >>> You should have 'vfs objects = dfs_samba4 acl_xattr recycle' >> >> Thank you very much for this - now it is working. This lack of >> permissions inheritance issue has been plaguing me for months - it is >> very

On 21/08/17 13:39, Robert Wolf wrote: > > On Mon, 21 Aug 2017, Sebastian Arcus wrote: > >> >> On 21/08/17 10:37, Gedalya wrote: >>> On 08/21/2017 07:28 AM, voytek at sbt.net.au wrote: >>>> is there a 'preferred way'? should I tell users to use 143 over 993 ? or >>>> 993 over 143? or? >>> There is no concrete answer. There