similar to: rsync server complaining about vanishing files while they are not.

Greetings. Yep, I have set "use chroot = no" for the module and it works. The symlinks I have are created automatically by a tool and are absolute. But since "use chroot = no" handles well absolute links from root/, the transfer works A1. Thanks for your input, Wayne. Best regards, Hans Deragon -- Consultant en informatique/Software Consultant Deragon

Greetings. Currently, the --one-file-system applies to both the source and destination and this is a problem. In my source, I have a symlink pointing to a directory on another device which I would like to have copied. I thus use --copy-unsafe-links. I also use --delete. This is dangerous because if there is a bug in my script, I would not like the destination to become suddenly

Greetings. If I do this: rsync --hard-links one.server.com::"module/somedir/images/redhat/3.0WS/en/os/i386 module/someotherdir/1.0/images/redhat/3.0WS/en/os/i386" /export/distros I get: /export/distros/i386/... and a conflict between the two sources. I want for destination: /export/distros/images/redhat/3.0WS/en/os/i386 /export/distros/1.0/images/redhat/3.0WS/en/os/i386 In other

Greetings. Total newbie with Ext3. I selected when I upgraded my system to RH7.2. I upgraded my system again to RH8.0. Here is some info: [root@world root]# cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw 0 0 /proc /proc proc rw 0 0 usbdevfs /proc/bus/usb usbdevfs rw 0 0 none /dev/shm tmpfs rw 0 0 none /dev/pts devpts rw 0 0 /dev/hdd1 /mnt/genericdata1 ext2 rw 0 0 Ok, so

I get a crash when I try to link multiple modules registered in their individual contexts. Documentation for Linker::LinkModules doesn't mention anything about contexts, and the first link succeeds. But the second link crashes. Is this not the right way to merge such modules? If not, then what is the right way? In any case, documentation for Linker::LinkModules should say if contexts are

> On 2015-Jun-01, at 11:06, Reid Kleckner <rnk at google.com> wrote: > > I'm pretty sure module linking is expected to occur in the same LLVM context. Correct. > IIRC Duncan had some proposal for how ld64 could do something clever with multiple contexts, but I've totally forgotten what it was. This was for LTO (probably unrelated to Yuri's scenario?). 1.

Yep I tried those two options, and nothing... Even if the pre-user conf files have a log file in the same directory, which I touch before trying, messages keep going to syslog... I tried with 666 permissions on rsyncd.log too just to make sure... The following is one of the user's conf file, hope theres a clue. Thanks! log file = /home/pluto/rsyncd.log <<< This is the problem!!

Being a bit of a neat freek, I would like to organize the models in my Rails app into modules. I have created the directory structure as follows: models |- module1 |- mymodel.rb And my model class code is: module Module1 class Mymodel ...some stuff end end How do I include this model in my controllers without referencing it as "Module1::Mymodel"? Also, how do I

Hi all, I am new to puppet, and I am trying to manage a windows agent using puppet. I wrote a manifest file which will copy a text file from puppet master (linux) to the puppet agent(windows). When I tried to run the puppet agent, I was getting the following error. err: /Stage[main]/Module1/File[change-ip.bat]: Failed to generate additional resources using ''eval_generate: Error

Please, help me understand if 'use chroot' option in daemon config is secure enough. Rsync manual has following lines: As an additional safety feature, you can specify a dot-dir in the module's "path" to indicate the point where the chroot should occur.  This allows rsync to run in a chroot with a non-"/" path for the top of the transfer

Just ran into this bug when running the latest snapshot from CVS: when rsyncing from two source directories into a third one, rsync gets confused about which source file is from which directory, resulting in a "file vanished" error. See test script below. Also, is there any consensus on whether using multiple source modules when pulling from an rsync daemon is going to be ok? I

In rsyncd.conf I'd like to be able to specify something like: [module1] gateway 10.168.172.9 or (I think we have to change the protocol a little for this one): [module2] redirect datasource.my.domain I've run into this need a few times, and I think it might be useful enough to add (both of these) to the daemon configuration. I'm asking the list to see if either of these might

LLVM (2.7 release version) provides 2 implementations for inlining function callsites: - InlineSimple.cpp (-inline): inline simple callsites according to its cost analysis - InlineAlways.cpp (-always-inline): inline all callsites that are marked with "always_inline" attribute. They are both subclasses of Inline.cpp that assumes the function's definition (body) is

On Tue, Jul 27, 2010 at 7:46 AM, Chuck Zhao <czhao at eecg.toronto.edu> wrote: >  LLVM (2.7 release version) provides 2 implementations for inlining > function callsites: > > - InlineSimple.cpp (-inline):               inline simple callsites > according to its cost analysis > - InlineAlways.cpp (-always-inline):  inline all callsites that are > marked with

I want to start out with an apache class that will disable all modules except for a pre-defined list, thus establishing a baseline of active modules. Then as needed, other classes could enable a module that they require that would have been disabled by the baseline state. Its possible several classes may try to enable the same module (1 or more classes needing module1 could be on a single node)

Hi! I am using Samba 3.0.4 + CUPS as a print server for a lot of windows machines. Since some days, all shared printers are gone every morning. Printers are still accessible in CUPS, but if you open a windows explorer and view the shares of the print server... there's nothing. Printing also does not work. Restarting samba & winbind solves the problem until the next morning. Does

We have a WAN with subnets and our remote SAMBA Hosts vanish after about a month from the WINS server. We have mixed SAMBA versions from 2.0.7 to 2.2.1a. NT (wins) 10.1.1.1 SAMBA 1 10.1.1.2 | | | SAMBA 2 10.2.2.2 All SAMBA hosts are set up to use the NT WINS server and after a SAMBA start they are there. But they 'fade away' in time. Is there a setting I am missing? Or do I

We're using a couple of HP printers (2200, 4200, 3390) using the HP PCL 6 printer driver. Printer drivers are installed on the samba (3.0.24) box, connecting, driver installation and printing work OK. Problem: using the same driver version with the printer shared by a windows box gives some additional options like - brochure printing - putting serveral pages on one sheet Any Idea why

mtex[3]<-"I need\'s a \"double quote\" with no backslash" mtex[3] [1] "I need's a \"double quote\" with no backslash" so how is it done? Thanks in advance, graham lawrence _________________________________________________________________ -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list --

platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status major 2 minor 6.0 year 2007 month 10 day