similar to: naming list entries dynamically

Displaying 20 results from an estimated 2000 matches similar to: "naming list entries dynamically"

2004 Feb 06
4
memory reduction
As those of you who watch CVS will be aware Wayne has been making progress in reducing memory requirements of rsync. Much of what he has done has been the product of discussions between he and myself that started a month ago with John Van Essen. Most recently Wayne has changed how the file_struct and its associated data are allocated, eliminating the string areas. Most of these changes have been
2008 Apr 23
3
select rows from data based on a vector of char strings
Hi, I have loaded a dataset in R : data = label freq1 freq2 news 54 35 fun 37 21 milk 19 7 food 3 3 .... etc And I have a vector flist<-c("fun","food") Now I want to use the vector 'flist' for selecting these values from 'data' so that I get the following dataset : label freq1 freq2 fun 37 21 food
2002 Mar 13
2
[PATCH] fix install-strip target in Makefile
The first patch will make "make install-strip" work. The second spends a few cycles avoiding "1 files to consider." Both are trivial but IMHO useful. --- Makefile.orig Wed Mar 13 06:38:42 2002 +++ Makefile Wed Mar 13 06:40:58 2002 @@ -12,6 +12,7 @@ LDFLAGS= INSTALLCMD=/bin/install -c +INSTALLMAN=/bin/install -c srcdir=. @@ -56,8 +57,8 @@ ${INSTALLCMD} -m 755 rsync
2008 Dec 07
1
unexpected scoping behavior with functions created in a loop
Hi guys. I recently stumbled on an unexpected behavior of R when using functions created in a loop. The problem is silly enough to me that I had hard time choosing a good mail subject, not talking about searching in the archives... After some experiments, I trimmed down the following minimal reproducible example: ####### makeF <- function(i) function() i fList <- list(makeF(1), makeF(2))
2008 Jan 21
2
experiments with slot functions and possible problems NOTE
Hello, first of all, thanks to LT for \pkg{codeutils}. I agree that it is indeed very useful to identify errors and also to encourage re-thinking past solutions. My problem: I want to compare different sets of related sub-functions which should be used alternatively by the same top-level function. Sets of related functions should be bound together (as lists) and the workspace should be as clean
2004 May 02
1
SEGV on FreeBSD 4.8-STABLE with 2.6.2
I'm getting a SEGV on a FreeBSD 4.8-STABLE box. The client is Solaris 9/SPARC. Both boxes run 2.6.2. The command I'm running is: $ rsync -arHRv --numeric-ids --delete --exclude=/opt/dist/cdrom \ [paths] [server]:[path] If I whittle down what appears in [paths], then it works. $ gdb rsync rsync.core gdb> bt #0 0x280faf0d in strncmp () from /usr/lib/libc.so.4 #1 0x7 in ?? () #2
2007 Nov 10
3
Funny issue with chroot + symlink outside chroot
Hi, The problem I found is not in what rsync, but on the error handling: How to reproduce: On server side I setup a tree and share using rsync + xinetd, of course, for security reason I use chroot option. Now I push this symlink: lrwxrwxrwx 1 root root 4 nov 10 16:28 horsroot -> /bin/ Now I try to do: ./rsync -avPH --copy-unsafe-links draco::test/ /tmp/rsyncdest/ (Of course the
2004 Jan 27
1
Differentiating debug messages from both sides
Some of the debug messages that rsync outputs (when verbose >= 2) can occur on both sides of the connection. This makes it hard to know which program is saying what. Some debug messages deal with this by outputting a "[PID]" string at the start of the message. Unfortunately, the startup message that tells us which pid is which is only output when verbose >= 3, so there's a
2010 Jan 24
1
auto reading in multiple txt files with filename as 1st column "ID"
Hi, I have many .txt files which look like this: 2009/02/07 12:30:10.0 ? ? ?5.0161 ? ? ?13.208 2009/02/07 12:45:10.0 ? ? ?5.0102 ? ? ?13.350 2009/02/07 13:00:10.0 ? ? ?5.0044 ? ? ?13.473 .... .... .... 2009/02/07 16:30:10.0 ? ? ?4.9366 ? ? ?13.788 2009/02/07 16:45:10.0 ? ? ?4.9397 ? ? ?13.798 end data. ###I can read in all files from "my_folder" using the following code:
2003 Aug 24
1
readdir() and read() errors ignored
We've just been hit rather badly by a very nasty bug that can cause rsync to silently discard files or fill them with zeroes. It happens when e.g. opendir() succeeds but readdir() returns an error; rsync does not check for an error from readdir() and so simply ignores the error (along with any remaining files in the directory). No error is reported to the user, who will then happily
2010 Feb 17
1
Problems transferring from older version of rsync to new
I have a system running rsync in daemon mode, the version information: > rsync --version rsync version 2.6.8 protocol version 29 On another system I have: > authoritative# rsync --version rsync version 3.0.7 protocol version 30 I have the following problem when trying to fetch files from the system running the old daemon: # /usr/local/bin/rsync --protocol=29 -vvvvvvvv
2004 Jan 13
3
Progress reporting: N more to check
A recent posting here got me thinking about having the --progress output tell the user about how many files were left to go in the transfer. I submit the attached patch which outputs an extra suffix onto the progress line at the end of each file's transfer (so it only appears once per file, not on every status update). The output would look like this: [...] flist.c 35671 100%
2007 Dec 13
3
rsync 3.00pre6 segfault in add_dirs_to_tree
Hi All I run rsync in an automated environment and it sometime will crash and leave a core dump file. from core dump, gdb shows that gdb) bt #0 add_dirs_to_tree (parent_ndx=-1, from_flist=0x56c590, dir_cnt=1) at flist.c:1422 #1 0x0000000000409eab in send_file_list (f=16, argc=-1, argv=0x56c238) at flist.c:2068 #2 0x0000000000419052 in client_run (f_in=16, f_out=16, pid=-1, argc=1,
2008 Jun 04
1
3.0.3pre2 compile warnings on interix
All seems to compile ok but I get the following warnings on interix 3.5 flist.c: In function `recv_file_entry': flist.c:840: warning: comparison between signed and unsigned flist.c:874: warning: comparison between signed and unsigned flist.c:876: warning: right shift count >= width of type flist.c: In function `make_file': flist.c:1178: warning: comparison between signed and unsigned
2004 Sep 29
2
defining a template for functions via do.call and substit ute.
Here's one not-so-straightforward way: > f <- function(a, b) a + b > flist <- as.list(f) > names(flist)[1:2] <- c("x", "y") > flist[[3]] <- do.call("substitute", list(body(f), list(a=as.name("x"), b=as.name("y")))) > g <- as.function(flist) > g function (x, y) x + y HTH, Andy > From: john.gavin at ubs.com
2003 Dec 30
3
The dangers of static buffers in rsync code
I have been trying for quite a while now to understand why is the flist.c:f_name() function implemented using static buffers. Anyone care to comment? The immediate problem is that any call to f_name overrides the previous content (well, obvious). This, combined with the fact that several function calls are made with the result of f_name(file) results in problems handling hardlinks - and
2002 Jul 31
1
rsync: omit summary with a single -v
It would be nice if there were a flag which would have rsync behave like a single -v but which would skip the two line summary info. I do a lot of cron-based transfers and I want to see what gets transferred if anything does, but I'd like it to be entirely silent otherwise. Here is a patch which makes a single -v behave this way. -vv causes it to include the extra info. diff -r -X
2002 Dec 05
1
Patch to ignore exluded files.
I came up with a patch to fix the problem of IO Errors caused by excluded files as did Eugene V. Chupriyanov below. Is there a chance that this change will show up in a future version of rsync? Is there a reason that we should not ignore IO errors when copy_links is off? Just want to make sure that I'm not missing something here that may corrupt my syncs.... Here's the version that
2002 Mar 12
2
Patch: --drop-suid Remove suid/sgid from target files
The attached patch adds an option --drop-suid which caused rsync to drop setuid/setgid permissions from the destination files. ie, even if the source file is setuid, the target file will not be. Added as we want to rsync the same files to machines both inside and outside our firewalls. For machines inside the firewall some files should be suid, for machines outside the firewalls they should
2007 Dec 19
1
3.0.0pre7 compiler warning on ia64
Any concerns with the compiler warning on flist.c on a ia64 system running SLES10SP1? ~/rsync-3.0.0pre7> make gcc -std=gnu99 -g -O2 -DHAVE_CONFIG_H -Wall -W -o mkrounding -I. ./ mkrounding.c ./mkrounding >rounding.h Rounding file_extras in multiples of 2 (EXTRA_LEN=4, FILE_STRUCT_LEN=24) gcc -std=gnu99 -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c flist.c -o flist.o /tmp/ccqjJwNs.s: