similar to: DO NOT REPLY [Bug 4412] New: --dry-run output inaccurate due to implied symlink

https://bugzilla.samba.org/show_bug.cgi?id=2390 Summary: some dry run stats inaccurate Product: rsync Version: 2.6.4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: woodd@deshaw.com QAContact:

https://bugzilla.samba.org/show_bug.cgi?id=2390 ------- Additional Comments From woodd@deshaw.com 2005-02-24 17:21 ------- Created an attachment (id=980) --> (https://bugzilla.samba.org/attachment.cgi?id=980&action=view) Proposed sender.c / receiver.c patch -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: -------

https://bugzilla.samba.org/show_bug.cgi?id=3844 Summary: --delete with --dry-run no longer reports files to be deleted Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=3422 Summary: dry run fails when encountering dangling symbolic link Product: rsync Version: 2.6.4 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

Wayne, Attached is a patch worth of suggested man page improvements for --no-implied-dirs and --keep-dirlinks. I think new users would find my explanations clearer and more complete, although you may want to make additional changes. I regenerated rsync.1 and the patch includes changes to it, but my yodl is somewhat weird, so I suggest you run yodl again yourself. -- Matt McCutchen

My CDR is displaying wildly inaccurate results. When I make a call the CDR records the time between connecting into the server and hanging up, instead of recording the time between dialling from the server to the PSTN destination via VOIP termination. It is alright to log the duration of the connection to the server, but why it does not log calls for termination via voip provider is the main

Brian Ripley writes today: >> There is already a usable log1p implementation in src/nmath/log1p, for >> platforms without it. All we need to do is to arrange to use it on those >> systems with broken versions. That's not easy without access to such a >> platform to test it, though. I need the same kind of test in my own software, so I made some experiments and

Hi, using R64.1 the summary function for simple statistics of a vector gives inaccurate results for the maximum. Example: summary(c(123456,1,2,3)) gives : Min. 1st Qu. Median Mean 3rd Qu. Max. 1.00 1.75 2.50 30870.00 30870.00 123500.00 The Max value ist wrong in a mathematical sense. I've tried with S-Plus, it gives the same result, but this seems

The following comment: 00881 // As a hack, we allow "align 2" on functions as a synonym for "alignstack 00882 // 2". in "lib/AsmParser/LLParser.cpp" appears inaccurate, the "alignment" is later parsed as the alignment of the function itself, both when directly placed on the function: 02975 // If the alignment was parsed as an attribute, move

I haven't looked inside to see what is causing this, but there's a big discontinuity in qgamma: curve(qgamma(x, shape=19), from=1e-10, to=2e-10) This appears in both R-patched and R-devel. Duncan Murdoch

https://bugzilla.mindrot.org/show_bug.cgi?id=3579 Bug ID: 3579 Summary: OpenSSH trims last character of fixed-lenght buffers received from the pkcs11 providers providing users with inaccurate information Product: Portable OpenSSH Version: 9.3p1 Hardware: Other OS: Linux

Dear All, Hans Borchers and I have been trying to compute "exact" derivatives in R using the idea of complex-step derivatives that Hans has proposed. This is a really, really cool idea. It gives "exact" derivatives with only a minimal effort (same as that involved in computing first-order forward-difference derivative). Unfortunately, we cannot implement this in R as the

Here's a contribution from Ian Smith that got bounced from the list. -------- Original Message -------- Subject: Re: [Rd] pt inaccurate when x is close to 0 (PR#9945) Date: Thu, 11 Oct 2007 06:02:43 -0400 From: iandjmsmith at aol.com To: murdoch at stats.uwo.ca Duncan, I tried sending the rest of this to R-devel but it was rejected as spam, hence the personal e-mail. R calculates the pt

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: normal In the tls section: it fails to mention the better solution (apt-get install libc6-xen) In the kernel section: where it says "for now we cannot provide precompiled Linux kernels with the xen patch applied", that's not true either. apt-get install linux-image-2.6-xen-k7 or some such. -- System Information: Debian

http://bugzilla.mindrot.org/show_bug.cgi?id=682 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From djm at mindrot.org 2004-03-30 16:15

Can anyone help make sense of this? This is an ext3 partition. It's only showing 403GB out of 426GB used, but then it says only 632MB available? Where'd the extra ~25GB go? [scarolan at server]$ df -H /disks/vrac5 Filesystem Size Used Avail Use% Mounted on /dev/sdb2 426GB 403GB 632MB 100% /disks/vrac5

If I run this: find /path/to/files/ -type f -mtime -2 -name *.xml.gz I get the expected results, files with modify time less than two days old. But, if I run it like this, with the print0 flag: find /path/to/files/ -print0 -type f -mtime -2 -name *.xml.gz I get older files included as well. Anyone know why?

Ray Brownrigg <ray@mcs.vuw.ac.nz> writes today about the log1p() problems on NetBSD 1.6 and OpenBSD 3.2: >> Indeed, but since I have acess to a NetBSD developer, this is an >> opportunity to get it fixed for everyone. That's a start, but the reality is that it isn't enough. There will be many sites that don't upgrade O/S versions except at possibly very long

Full_Name: Jim Breaux Version: 1.9.0 OS: WinXP Submission from: (NULL) (209.78.110.135) According to the help for 'round' it is supposed to round to the even digit. However, see the following examples: In the following, R is rounding down: > round(0.3645, 3) [1] 0.364 > round(0.3655, 3) [1] 0.365 > round(0.3665, 3) [1] 0.366 > round(0.3675, 3) [1] 0.367 > round(0.3685,

Full_Name: Attila Lengyel Version: 2.8.0 OS: WinXP Submission from: (NULL) (81.182.224.160) > -0.3+0.1+0.1+0.1 [1] 2.775558e-17