search for: source_dir

...b/xen/debian/rules.real index 2265551..12fc4ae 100644 --- a/xen/debian/rules.real +++ b/xen/debian/rules.real @@ -247,6 +247,10 @@ install-utils-common: $(STAMPS_DIR)/install-utils-common dh_installinit --name xend dh_installinit --name xendomains --no-start -- defaults 21 20 dh_installman $(SOURCE_DIR)/docs/man1/* $(SOURCE_DIR)/docs/man5/* + dh_installdocs $(SOURCE_DIR)/docs/txt/misc/xl-disk-configuration.txt + dh_installdocs $(SOURCE_DIR)/docs/txt/misc/xl-network-configuration.txt + dh_installdocs $(SOURCE_DIR)/docs/txt/misc/xl-numa-placement.txt + dh_installdocs $(SOURCE_DIR)/docs/txt/misc/xen...

On UNIX, I am executing an rsync command, from within a script. The command goes something like this: /usr/bin/rsync --verbose --progress --stats --compress --recursive --times --perms --links --safe-links source_dir/ user at target_machine:/parent_path/source_dir In other words, I am replicating source_dir on a remote machine. It ends up next to a lot of sibling, directories, like this: On target_machine /parent_path/source_dir /parent_path/source_dir2 .... /parrent_path/source_dirn Here's my issue. I...

I have a function: source_dir <- function(path, pattern = "\\.[rR]$", chdir = TRUE) ... documented with ... \usage{source_dir(path, pattern="\\.[rR]$", chdir=TRUE)} ... But I get Codoc mismatches from documentation object 'source_dir': source_dir Code: function(path, pattern = "\\.[rR]$...

...b/xen/debian/rules.real index 2265551..3b610ea 100644 --- a/xen/debian/rules.real +++ b/xen/debian/rules.real @@ -247,6 +247,13 @@ install-utils-common: $(STAMPS_DIR)/install-utils-common dh_installinit --name xend dh_installinit --name xendomains --no-start -- defaults 21 20 dh_installman $(SOURCE_DIR)/docs/man1/* $(SOURCE_DIR)/docs/man5/* + dh_installman $(SOURCE_DIR)/tools/xenstat/xentop/xentop.1 + dh_installman $(SOURCE_DIR)/tools/xentrace/xentrace.8 + dh_installman $(SOURCE_DIR)/tools/xentrace/xentrace_format.1 + dh_installdocs $(SOURCE_DIR)/docs/txt/misc/xl-disk-configuration.txt + dh_insta...

Guys, I''m working with the new RadRails release (0.5.3), which has a very nifty inclusion of ri courtesy of RDT. Problem is, although I''ve generated rdoc for all installed gems with "gem rdoc --all", it''s not accessible through ri. I see some posts here and there about rimport...is this still the necessary way to incorporate the rails rdoc into ri?

I'm using a little shell script: BUILD_ROOT=/home/llvm-1.7/cfrontend PREFIX="$BUILD_ROOT/install" LOCAL_BUILD_DIR="$BUILD_ROOT/build" SOURCE_DIR="$BUILD_ROOT/src" echo $__me: Building $TARGET echo $__me: BUILD_ROOT == $BUILD_ROOT echo $__me: SOURCE_DIR == $SOURCE_DIR echo $__me: LOCAL_BUILD_DIR == $LOCAL_BUILD_DIR echo $__me: PREFIX == $PREFIX confopts="--prefix=$PREFIX" confopts="$confopts --disable-threads&q...

Greg Pettyjohn <gregp at ccs.neu.edu> writes: > Is the MinGW user's list on the web? Look on www.mingw.org -> mailing list > Can you give me a link to the thread? Sorry, no time for that. Once on the mailing list archives, do a search for 'configure'. > (What's IIRC?) If I Remember Correctly. By the way, what's your configure command? -- Oscar

Is the MinGW user's list on the web? Can you give me a link to the thread? (What's IIRC?) Thanks. On Sat, 22 Apr 2006, Oscar Fuentes wrote: > Greg Pettyjohn <gregp at ccs.neu.edu> writes: > > > I've blown a couple of weekends trying to build under MinGW. > > > > I can build the llvm tools with only a couple of minor hassles, but can't > > seem

Hi all, I'm running the following rsync job via cron: rsync --recursive --compress --human-readable --progress --update --perms --chmod=a-w -e "ssh -i /rsync-key" user@host:/source_dir/ /target_dir rsync: failed to set permissions on "/target_dir/.": Operation not permitted (1) rsync: failed to modify permissions on "/target_dir/.": Operation not permitted (1) rsync: failed to set permissions on "/target_dir/.": Operation not permitted (1) rsync err...

...l." operation. I am parsing the log file in a subsequent java program and that is where I ran into a problem: In the log file all lines with deleted files do not show the full path to the deleted files but show the path of where I ran the rsync command and the deleted file name. Example: source_dir/test1 destination_dir/test1 Now I delete the file test1 in source_dir and run rsync in the directory "script" Then I would expect in the log file a line like: source_dir/test1 2006/12/21 18:49:58 del. 0 but I get: script/test1 2006/12/21 18:49:58 del. 0 Is this a bug or am I the bug...

...hen used as a compiler 'compiler' = compiler { # Inherit from generic compiler prototype # Inputs param flags : list[string] # Compiler-specific flags param include_dirs : list[string] param sources : list[string] param outputs : list[string] param source_dir : string param warnings_as_errors : bool # Generic compiler flags param all_warnings : bool # " # Outputs compile => [ # '=>' means dynamic evaluation message.status("Compiling ${sources[0]}\n") command('clang',...

...ot;$confopts --disable-shared" > confopts="$confopts --enable-languages=c,c++" > confopts="$confopts --disable-c-mbchar" > confopts="$confopts --program-prefix=llvm-" Try adding --disable-fixincludes too. [snip] > ../src/configure --srcdir=$SOURCE_DIR > --includedir=/C/msys/1.0/mingw/include --libdir=/C/msys/1.0/mingw/lib > --target=mingw32 $confopts --includedir and --libdir should be Windows directories (c:/msys/...). MinGW does not understand Cygwin/MSYS paths. Is --srcdir really needed? > make CFLAGS=-O LIBCFLAGS+=-g LIBCFLAGS...

...ubygems'' require ''puppetlabs_spec_helper/module_spec_helper'' * Create a .fixtures.yml file: fixtures: repositories: "stdlib": "git://github.com/puppetlabs/puppetlabs-stdlib" symlinks: "MY_MODULE": "#{source_dir}" Other dependency modules can be added to the "repositories" section. * Run ''rm -r spec/fixtures''. The rake task will populate the fixtures directory for you based on your .fixtures.yml Once these steps are completed, you can execute ''rake spec'...

Thank you Kevin. It seems that I misunderstood the purpose of this --delete-missing-args option. If someone has a good suggestion on how to rsync a list of files and delete from the destination any file that is not listed in --files-from, that would be welcome. Thanks, MI -------- Original Message -------- (Kevin Korb via rsync, 2019-04-23 14:11) > --files-from will delete files from

...Migration Facility (DMF). A typical command we use is the following (but I have shortened the paths and addresses). rsync --password-file=not_for_your_eyes --numeric-ids -a --stats --one-file-system --max-size=8.0GB --warn --whole-file --link-dest=previous --delete root at source_host::backups/source_dir current --password-file=not_for_your_eyes . for the daemon --numeric-ids . since the userids on the source are not always available on the destination -a . archive mode --stats . statistics --one-file-system . stops the backup of everything when backing up / --max-size=8.0GB...

...s what I want it to do and I'm not worried about error messages). What seems to be happening is that even though the directory doesn't exist and the temporary file can't be created the data is transferred but not written anywher e.g. /usr/local/bin/rsync --stats -lptgoDvxe ssh sender:/source_dir/ORACLE/dsk03/ORACLE/DIR/somefile.dbf /dest_dir/dsk03/ORACLE/DIR/somefile.dbf rsync: mkstemp "/data00/dsk03/ORACLE/DIR/.somefile.jDaGKh" failed: No such file or directory (2) Number of files: 1 Number of files transferred: 1 Total file size: 839917568 bytes Total transferred file size: 8...

> On Jan 12, 2016, at 9:39 AM, Reid Kleckner <rnk at google.com> wrote: > > Sounds like a plan. > > Should we leave behind a simple ./configure script that checks for cmake, and if present, runs something like 'cmake -G"Unix Makefiles" .'? I think it's nice if the "standard" Unix way of building with "./configure && make"

...utes, offset by 5 minutes). All machines are running rsync v2.5.6, and using ssh2 v3.2.3 as the transport rather than rsh. The commands used to rsync to both clients are exactly the same: /usr/local/bin/rsync -rltvR -e "/usr/local/bin/ssh2 -x" \ --size-only --delete <source_dir> <destination_host>:<dest_dir> The destination directory on both clients for the files/directories being mirrored is a samba share, the active share being on client A, and the backup(inactive) share on client B. The files in the share, and the samba share itself are...

...============= > > --- cmake/modules/LLVMExternalProjectUtils.cmake > > +++ cmake/modules/LLVMExternalProjectUtils.cmake > > @@ -29,7 +29,8 @@ > > # Extra targets in the subproject to generate targets for > > # ) > > function(llvm_ExternalProject_Add name source_dir) > > - cmake_parse_arguments(ARG "USE_TOOLCHAIN;EXCLUDE_FROM_ALL;NO_INSTALL" > > + cmake_parse_arguments(ARG > > + "USE_TOOLCHAIN;EXCLUDE_FROM_ALL;NO_INSTALL;ALWAYS_CLEAN" > > "SOURCE_DIR" > > "CMAKE_ARGS;TOOLCHAIN_TOOL...

Memory leaks found by the tool--valgrind along with static reviewing. Based on Daivd''s branch ''integration-20130903''. Gui Hecheng (5): btrfs-progs:free local variable buf upon unsuccessful returns btrfs-progs:local variable memory freed btrfs-progs: missing tree-freeing statements added btrfs-progs:free the local list pending_list in btrfs_scan_one_dir