similar to: question about 2.6.3pre2's --link-by-hash behaviour

Displaying 20 results from an estimated 3000 matches similar to: "question about 2.6.3pre2's --link-by-hash behaviour"

2004 Mar 26
1
2.6.1pre-1 Segmentation fault & other fun
Oops :) -- quote -- $ rsync -aHPv rsync://host/module/single.file . <motd, if any> receiving file list ... 1 file to consider Segmentation fault -- endquote -- The rsync process remains running until explicitly 'kill'ed. At which point, the following is printed: -- quote -- rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(225) -- endquote -- -- quote -- $ rsync -aHPv
2005 Mar 17
1
odd behaviour change (2.6.3 > 2.6.4pre3)
Synopsis: Prior to the 2.6.4pre versions, issuing 'rsync rsync://host/module/' behaved effectively as 'ls -l'. I've toyed with various options in an attempt to get an 'ls -l' style output, but to no avail. As I have a small handful of scripts that rely on this no-longer-functioning functionality, this could be considered a Bad Thing(TM). Following is an example of
2007 Oct 12
1
3.0.0pre2: non-recursive remote listing breakage
3.0.0pre2: non-recursive remote listing breakage Looks like pre1's fix broke something else. I noticed this when listing module/directory contents on servers known to be running versions 2.5.7 & 2.6.3. Not having (full) access to them, I replicated the errors using 2 machines on my home lan. # the machines lithium.elements.lan: the client. rsync 3.0.0pre2 for all tests.
2007 Oct 18
1
3.0.0pre2(cvs) error: check_for_finished_files: Assertion `flist != ((void *)0)' failed.
Just a quick heads up to say I'm still getting this (reproducable) error while doing daily backups: rsync: generator.c:1872: check_for_finished_files: Assertion `flist != ((void *)0)' failed. rsync: writefd_unbuffered failed to write 4092 bytes [receiver]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1500) [receiver=3.0.0pre2] This is with cvs
2007 Oct 16
3
To inc_recurse or not to inc_recurse? [Re: 3.0.0pre2: bookend breakage (2 different errors)]
On 10/15/07, Erik Jan Tromp <betageek@sympatico.ca> wrote: > # The second error > Invalid file index: -101 (-1 - 0) with iflags 0 [receiver] > rsync error: protocol incompatibility (code 2) at rsync.c(273) [receiver=3.0.0pre2] > rsync: connection unexpectedly closed (21 bytes received so far) [generator] > rsync error: error in rsync protocol data stream (code 12) at io.c(596)
2007 Oct 06
2
non-recursive remote listing breakage in 3.0.0pre1
It would appear something snuck in that breaks non-recursive remote listings when talking to a non-3.0.0pre1 version of rsync. The symptom itself is simple enough to see; rather than displaying member directories/regular files/symlinks/etc as one would expect, only non-directories (with the exception of '.') are listed. Other tidbits.. some obvious, some maybe not: - not limited to just
2010 May 01
4
[Bug 27928] New: Nouveau / Mesa sometimes gets libraries overwritten
https://bugs.freedesktop.org/show_bug.cgi?id=27928 Summary: Nouveau / Mesa sometimes gets libraries overwritten Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at
2005 Mar 29
2
Annotation metadata "kills" help.search
Greetings! OS: Windows R 2.0.1 Before anyone flames -- I tried to query this on the R searchable web site and using google and did not find anything applicable. As of about a week ago the help.search function dies when used in the simple help.search("something") usage. The error is Error in rbind(...) : number of columns of matrices must match (see arg 203) After some effort I have
2008 Mar 28
1
3.0.0pre2 error on module, fine on subdir
Just tripped over this one today. $ rsync --no-motd rsync://alphageek.dyndns.org/slackware rsync: link_stat "." (in slackware) failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1498) [receiver=3.0.1pre2] $ rsync --no-motd rsync://alphageek.dyndns.org/slackware/slackware-current drwxr-xr-x 4096 2008/03/26 01:30:27
2010 Jun 23
2
problem installing dotnet 2.0
when installing dotnet 2.0 the install crashes ive tried clearing winetricks cache but that doesn't seem to work here's the errors im getting any help is appreciated Code: lithium at lithium-laptop:~$ ./winetricks ------------------------------------------------------ Instaling .net 2.0 runtime. Can take several minutes. See http://wiki.winehq.org/MicrosoftDotNet for tips.
2011 Apr 17
1
Bug#623120: xen-utils-4.1: unable to start non-hvm VMs when using Xen 4.1
Package: xen-utils-4.1 Version: 4.1.0-2 Severity: important I had a working Xen server with 4.0 hypervisor and 2.6.32 kernels. After updating (and booting up) 4.1 hypervisor with 2.6.38 kernel, any attempt to create a VM failed (also the ones saved from previous book don't come up either). If I try to use xl : # xl create /etc/xen/lithium.vm.carpediem.sh.cfg Parsing config file
2006 Mar 13
2
feature request/change for 2.6.8
Wayne, I've been experimenting with the {pre,post}-xfer exec options ever since the original diff showed up in patches/ - fantastic stuff. My feature request/change centers around the new RSYNC_ARG# variables. Would it be possible to make these available as an array (ie: ${RSYNC_ARG[#]}) rather than discrete variables? If nothing else, it would greatly simplify chewing through all the args
2011 Feb 08
1
Just another pattern matching / indexing question
Hi all, thank you for your patience. I am dealing with a large dataset detailing patients and medications Medications are hard to code, as they are (usually) meaningless unless matched with doses. I have a dataframe with vectors (Drug1, Drug2..... Drug 16) and individual patients are represented by rows. The vectors are actually factors, with 100s of possible levels (all the drugs the patient
2004 Jul 30
0
Information on the DMC 800
The page to see this if you cannot see HTML on e-mail or just want to look at all of it is. Sometimes, if it is reasonable, people would prefer not to search around to web sites so I am posting highlights in HTML as well as giving the link. Could someone buy me a DMC-800 :-). Why I always look for components and off brands that focus on engineering rather than marketing is that they are not in the
2019 May 30
0
safety vulnerability in tablet computer
We discovered safety hardware vulnerability in Samsung tablet computer model SM-T580 16GB SN: R52M20EG5WR ? dangerous overheat of the tablet lithium-ion battery caused by short circuit to flash LED, which caused more likely by failed LED controlling hardware. We believe that similar design have other mobile computerized devices utilizing flash LED for digital camera. The computer in question has
2007 Dec 06
1
lm.influence under R2.6.1
Greetings! Recently when I tried to use lm.influence I get the following error: Error in .Fortran("lminfl", model$qr$qr, n, n, k, as.integer(do.coef), : Fortran symbol name "lminfl" not in DLL for package "base" This occurs on both Linux and Windows platforms (details below). Searching the mail lists and other sources indicates that the fortran code for
2003 Sep 08
4
Samba-3 Ldap Adding Administrator Account
How do you add an "Administrator" account to ldap. I want to leave root in /etc/passwd but have "Administrator" in ldap I have checked Howto Collection and the Samba-Ldap-3 but they contain no information. The Ldap-Howto has a suggestion but then says not to use. Godfrey
2013 Apr 10
1
[PATCH v3] x86: use a read-only IDT alias on all CPUs
Make a copy of the IDT (as seen via the "sidt" instruction) read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks, and has the added benefit of also not leaking the kernel base offset, if it has been relocated. We already did this on vendor == Intel and family == 5 because of the F0 0F bug -- regardless of if a particular CPU had the F0 0F bug
2013 Apr 10
1
[PATCH v3] x86: use a read-only IDT alias on all CPUs
Make a copy of the IDT (as seen via the "sidt" instruction) read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks, and has the added benefit of also not leaking the kernel base offset, if it has been relocated. We already did this on vendor == Intel and family == 5 because of the F0 0F bug -- regardless of if a particular CPU had the F0 0F bug
2013 Apr 08
3
[PATCH] x86: make IDT read-only
This makes the IDT unconditionally read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks. It has an added benefit of also not leaking (via the "sidt" instruction) the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> ---