search for: target_dir

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 error: some file...

...right line to add " && chmod 644", the actual resulting file still remains at 0600 ?!? #!/bin/bash # Usage: imapsieve_copy <email> <spam|ham> MSG_USER="$1" MSG_TYPE="$2" RUN_UUID=$(cat /proc/sys/kernel/random/uuid) BASE_DIR="/foo/bar" TARGET_DIR="${BASE_DIR}/${MSG_TYPE}" TARGET_FILE="${TARGET_DIR}/${RUN_UUID}" cat > "${TARGET_FILE}" < /dev/stdin && pigz -9 "${TARGET_FILE}"

...bus_comms.h" #define streq(a, b) (strcmp((a), (b)) == 0) diff -r 0229efe8ffe4 linux-2.6-xen-sparse/mkbuildtree --- a/linux-2.6-xen-sparse/mkbuildtree Mon Aug 8 18:43:57 2005 +++ b/linux-2.6-xen-sparse/mkbuildtree Mon Aug 8 15:15:06 2005 @@ -74,6 +74,25 @@ ) } +# relative_lnfiles <target_dir> <target_files> +# Creates a tree of symlinks in the current working directory that mirror +# <target_files> in <target_dir>. <target_dir> should be relative to the current +# working directory. Symlinks in <target_dir> are ignored. Source-control files +# are ignor...

...t;source> /absolute/path/to/file" exit 1 fi # The following is a very strange way to load last variable into RSYNC_TARGET (don't ask...) for RSYNC_TARGET; do :; done # If the destination we got is not /absolute/path/to/somewhere, append $TARGET_DIR # infact, if we got empty target, assume root of TARGET_DIR # If we get full path - assume user tell us where to put it if [ "${RSYNC_TARGET:0:1}" != '/' ]; then RSYNC_TARGET="$TARGET_DIR/$RSYNC_TARGET" # Else if we got o...

Hi all, I thought I'd share I script I made (based on some of Leif's works) that lets you download, compile and install Asterisk all in one go; and then removed the dev tools used. We use it quite a bit to provision systems using Ansible, but it is easier than remembering everything every time even if you are using a shell. At the moment I have scripts for Centos 7 and Asterisk 13, but

Otherwise, automake will fail to process vivified/code/Makefile.am --- configure.ac | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/configure.ac b/configure.ac index a3e186b..0e28374 100644 --- a/configure.ac +++ b/configure.ac @@ -300,6 +300,7 @@ else AC_MSG_NOTICE([Vivified was not enabled.]) fi AM_CONDITIONAL(HAVE_VIVI, [test "x$HAVE_VIVI" = xyes])

...ROP Scc_ProjName "" # PROP Scc_LocalPath "" CPP=cl.exe !IF "$(CFG)" == "libFLAC - Win32 Release" # PROP BASE Use_MFC 0 # PROP BASE Use_Debug_Libraries 0 # PROP BASE Output_Dir "Release" # PROP BASE Intermediate_Dir "Release" # PROP BASE Target_Dir "" # PROP Use_MFC 0 # PROP Use_Debug_Libraries 0 # PROP Output_Dir "Release" # PROP Intermediate_Dir "Release" # PROP Target_Dir "" # ADD BASE CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /YX /FD /c # ADD CPP /nol...

...he actual resulting file still remains at 0600 ?!? > > #!/bin/bash > > # Usage: imapsieve_copy <email> <spam|ham> > > MSG_USER="$1" > MSG_TYPE="$2" > > RUN_UUID=$(cat /proc/sys/kernel/random/uuid) > BASE_DIR="/foo/bar" > TARGET_DIR="${BASE_DIR}/${MSG_TYPE}" > TARGET_FILE="${TARGET_DIR}/${RUN_UUID}" > > cat > "${TARGET_FILE}" < /dev/stdin && pigz -9 "${TARGET_FILE}" You can run umask 0222 to change it. Aki

rsync+ is ready to go onto HEAD. Could Jos or somebody else who's used the feature before please prepare a few paragraphs for the manpage explaining how they work? Either send a patch to the .yo files or just plain text. Thanks, -- Martin

...v->config_len; if (size & (size-1)) size = 1 << qemu_fls(size); diff --git a/rules.mak b/rules.mak index 8d6d96e..defee1d 100644 --- a/rules.mak +++ b/rules.mak @@ -1,6 +1,6 @@ %.o: %.c - $(call quiet-command,$(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<," CC $(TARGET_DIR)$@") + $(call quiet-command,$(CC) $(CPPFLAGS) $(CFLAGS) -Werror -Wno-error=uninitialized -c -o $@ $<," CC $(TARGET_DIR)$@") %.o: %.S $(call quiet-command,$(CC) $(CPPFLAGS) -c -o $@ $<," AS $(TARGET_DIR)$@") -- 1.6.2.2

...v->config_len; if (size & (size-1)) size = 1 << qemu_fls(size); diff --git a/rules.mak b/rules.mak index 8d6d96e..defee1d 100644 --- a/rules.mak +++ b/rules.mak @@ -1,6 +1,6 @@ %.o: %.c - $(call quiet-command,$(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<," CC $(TARGET_DIR)$@") + $(call quiet-command,$(CC) $(CPPFLAGS) $(CFLAGS) -Werror -Wno-error=uninitialized -c -o $@ $<," CC $(TARGET_DIR)$@") %.o: %.S $(call quiet-command,$(CC) $(CPPFLAGS) -c -o $@ $<," AS $(TARGET_DIR)$@") -- 1.6.2.2

...v->config_len; if (size & (size-1)) size = 1 << qemu_fls(size); diff --git a/rules.mak b/rules.mak index 8d6d96e..defee1d 100644 --- a/rules.mak +++ b/rules.mak @@ -1,6 +1,6 @@ %.o: %.c - $(call quiet-command,$(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<," CC $(TARGET_DIR)$@") + $(call quiet-command,$(CC) $(CPPFLAGS) $(CFLAGS) -Werror -Wno-error=uninitialized -c -o $@ $<," CC $(TARGET_DIR)$@") %.o: %.S $(call quiet-command,$(CC) $(CPPFLAGS) -c -o $@ $<," AS $(TARGET_DIR)$@") -- 1.6.2.2

...v->config_len; if (size & (size-1)) size = 1 << qemu_fls(size); diff --git a/rules.mak b/rules.mak index 8d6d96e..defee1d 100644 --- a/rules.mak +++ b/rules.mak @@ -1,6 +1,6 @@ %.o: %.c - $(call quiet-command,$(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<," CC $(TARGET_DIR)$@") + $(call quiet-command,$(CC) $(CPPFLAGS) $(CFLAGS) -Werror -Wno-error=uninitialized -c -o $@ $<," CC $(TARGET_DIR)$@") %.o: %.S $(call quiet-command,$(CC) $(CPPFLAGS) -c -o $@ $<," AS $(TARGET_DIR)$@") -- 1.6.2.2

Hi, this series start to implement some of the changes needed to support d-i-b 2.0; normal VM distro builds seem to work correctly, ramdisk builds are still broken and require more efforts. Thanks, Pino Toscano (5): dib: implement get_image_element_array stuff dib: export IMAGE_BLOCK_DEVICE_WITHOUT_PART dib: extract get_required_tool out of require_tool dib: require a Python interpreter

...t I don't care if people look at the data. Typically, this mirroring has been done using just the local client's rsync program in conjunction with ssh (both on the client and sshd on the remote machine): rsync --delete --rsh ssh --rsync-path /path_to_rsync/rsync -rlpt sourcedir remote_host/target_dir/ The problem, however, is that due to the large size of the data, and the slowness typically suffered under encryption, the remote machine crawls to a halt or is seriously impaired. Working with small numbers of files or infrequent mirrors, the encryption is not a problem, but it gets to be a burd...

...- destdir libdir hooksdir tmpdir fakebindir all_elements element_paths = + destdir libdir hooksdir fakebindir all_elements element_paths = let network_string = if network then "" else "1" in let run_extra = sprintf "\ #!/bin/bash set -e %s +mount_dir=$1 +shift target_dir=$1 shift script=$1 @@ -87,7 +89,7 @@ shift export PATH=%s:$PATH # d-i-b variables -export TMP_MOUNT_PATH=%s +export TMP_MOUNT_PATH=\"$mount_dir\" export DIB_OFFLINE=%s export IMAGE_NAME=\"%s\" export DIB_ROOT_LABEL=\"%s\" @@ -120,7 +122,6 @@ $target_dir/$scrip...

...-with-lockdir=/tmp/samba \ --with-piddir=/tmp/samba \ --with-swatdir=/tmp/samba \ --with-privatedir=/etc/samba/private \ --with-sendfile-support \ --with-ldap \ --with-ads \ --with-krb5=$(TARGET_DIR)/usr/lib \ --with-pam \ --with-pammodulesdir=/lib/security \ --with-pam_smbpass \ --with-winbind \ --with-acl-support \ --with-cifsumount \ --with-libiconv=$(TARGET_DIR)/usr \...

...S-Cache: Netfs '9p' registered for caching 9pnet_virtio: no channels available and `mount` complains that the source (tag) doesn't exist when trying to mount the filesystem share again. For the record, the mount command I always use is simply: mount -t 9p -o trans=virtio $TAG $TARGET_DIR I've tried setting `-o debug=0xfff` but I get no debug info at all. Is it expected behaviour that filesystem shares get into a broken state after restoring a snapshot? If it's of any relevance, here's some more context: * The host is running Debian Jessie with Linux 3.16.7-ckt9-3~de...

Move the OCaml binding to C _exit to an own module. Just code motion, adapting v2v in the process. --- docs/C_SOURCE_FILES | 2 +- mllib/Makefile.am | 5 ++++- mllib/exit-c.c | 33 +++++++++++++++++++++++++++++++++ mllib/exit.ml | 19 +++++++++++++++++++ mllib/exit.mli | 20 ++++++++++++++++++++ v2v/Makefile.am | 1 - v2v/changeuid-c.c | 33

Without this option, configure will fail when there is no display. Signed-off-by: Masami HIRATA <msmhrt at gmail.com> --- configure.ac | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/configure.ac b/configure.ac index de8a064..61d6f69 100644 --- a/configure.ac +++ b/configure.ac @@ -593,16 +593,16 @@ working. AC_MSG_FAILURE([$QEMU version must be >=