similar to: Rsync shouldn't display a meaningless speedup on a dry run

https://bugzilla.samba.org/show_bug.cgi?id=4757 Summary: Daemon mis-logs paths if module path in rsyncd.conf is relative Product: rsync Version: 3.0.0 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

What is the official syntax for pulling multiple sources from a daemon? In analogy to a remote shell, I expected this to work: rsync rsync://matt@mattlaptop2:3141/module/'foo bar' dest/ But it doesn't; the daemon tried to access a file 'foo bar' with a space in its name. Using a newline like this does work because the newline becomes an argument delimiter in the daemon

Hello, I was implementing the llvm_any_type in my intrinsic def int_csa_xxx : Intrinsic<[llvm_any_ty], [llvm_i32_ty]>; as the following in its corresponding builtins in Builtins.def: BUILTIN(__builtin_xxx, "v.", "nt") the "t" was sufficient here to not perform any type checking. The type checking was handled in CGBuiltin.cpp. This was working until

I try to use the routine cutree to cut a tree (created by hclust) into several groups by specifiing the hight of the cut. a<-1:10 cutree(tree, h=a*100) The Matrix with group meberships returned is ok for most of the hights, but in some cases (as for example h=800 and h=900) the results don't make sense (group membership=0 or 58965231, it looks like the range of data allowed by the data

https://bugzilla.mindrot.org/show_bug.cgi?id=2252 Bug ID: 2252 Summary: RekeyLimit breaks ClientAlive Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org

https://bugzilla.mindrot.org/show_bug.cgi?id=2279 Bug ID: 2279 Summary: ListenAddress option does not allow IPv6 link-local addresses Product: Portable OpenSSH Version: 6.6p1 Hardware: Other OS: Other Status: NEW Severity: normal Priority: P5 Component: sshd

Just saw this from eWeek. "IBM, which paid roughly $500,000 for the testing, and SuSE (pronounced "SOOS-ah") were announcing the certification jointly. " The article is here: http://www.eweek.com/article2/0,3959,1212529,00.asp --- Darren Reed <avalon@caligula.anu.edu.au> wrote: > In some mail from twig les, sie said: > > > > I actually just asked

On Wed, Jun 13, 2012 at 11:43 AM, Andrew Trick <atrick at apple.com> wrote: > > On Jun 13, 2012, at 7:15 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > Again, this is branch code, but if I can see something wrong in platform > independent portion, I'll track it on the trunk. > > > I hate to be the one to start this thread, but I have to say it at

John Todd's Onlamp article mentions an OpenBSD version as of June 2003. Have I been sleeping while reading asterisk-users? Is it a seperate project or is it just making Asterisk portable? Who is working on this and is it in the main CVS yet? Do they have device drivers ported or just the software parts of Asterisk? I think the software parts would be relatively simple but time consuming.

On 30 April 2010 11:43, Sherief N. Farouk <sherief at mganin.com> wrote: >>> I'm a software engineer. I'm terribly uncomfortable with C. > > Aaaaahahahahahahahaha Please be civil, guys. Different engineers have different skill levels, so what. If someone asks for some help with the reference implementation the least we can do is point them in a useful direction. If

Samba organizers might want to look into this: [ns1:~] dig 150.73.70.66.relays.osirusoft.com ; <<>> DiG 9.2.2 <<>> 150.73.70.66.relays.osirusoft.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28005 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 13 ;; QUESTION SECTION:

On Jun 13, 2012, at 7:15 AM, Sergei Larin <slarin at codeaurora.org> wrote: > Again, this is branch code, but if I can see something wrong in platform > independent portion, I'll track it on the trunk. I hate to be the one to start this thread, but I have to say it at least once... General advice. Working off trunk will be less painful than cherry-picking. When it comes to

Hi, As far as I can see, the only way you can tell it's been a dry-run at the receiver-side, is to parse RSYNC_ARGs in the pre-xfer script. I think the only way is to crawl through the RSYNC_ARGs to find a value which: - starts with a single dash, and; - contains 'n', and; - comes prior to the "." value, signifying the start of the 'path args' (which seem inherently

T. Shandelman via rsync wrote: > Rsync is a remarkably handy tool that I use virtually every day. > > But there is one thing about rsync that drives me totally crazy. > > Under the -n (dry run) flag, rsync seems to produce exactly the same output > as without that flag. > > I cannot tell you how many times I sit and scratch my head long and > hard,after I discover

This implements -dry-run for llvmc2: $ llvmc2 -dry-run main.c llvm-g++ -c -x c main.c -o /tmp/llvm_bGw2gN/main.bc -emit-llvm llc -f /tmp/llvm_bGw2gN/main.bc -o /tmp/llvm_bGw2gN/main.s llvm-gcc -c -x assembler /tmp/llvm_bGw2gN/main.s -o /tmp/llvm_bGw2gN/main.o llvm-gcc /tmp/llvm_bGw2gN/main.o -o a.out $ llvmc2 -dry-run -opt main.c llvm-g++ -c -x c main.c -o /tmp/llvm_UGZtwL/main.bc -emit-llvm opt

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:

Is there anyway on a dry-run to actually see per file how many bytes are to be transferred? On a normal run I use --log-format=/%f/%l/%b/%i which shows the total file size and the actual bytes transferred. Also, during a dry-run, is there anyway to show the Literal Data? Basically, I'm trying to calculate something before the actual run takes place. Dry-run is telling me which files have

https://bugzilla.samba.org/show_bug.cgi?id=10799 Summary: Feature request: detail --dry-run mode when --debug=exit Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org

I was working on a backup script today and doing lots of runs with the --dry-run option to make sure I had things the way I wanted them. One particular filesystem I was backing up always hung right as it should have been finished. (This happened every time I did a dry run, it was 100% reproducible). Several other filesystems I was backing up had no problems of any kind with the dry run using the

Try as we may (--dry-run), it still won't tell us where it intends to put the files, $ rsync --dry-run --remove-source-files --relative --verbose --itemize-changes -Cavz Maildir/new /tmp/ sending incremental file list delta-transmission disabled for local transfer or --whole-file cd+++++++++ Maildir/ cd+++++++++ Maildir/new/ >f+++++++++ Maildir/new/1546157908.1392_1.jidanni7 total: