search for: global_opts

...atch to CVS to also permit EINVAL. Question for IPv6 experts: why check the errno code at all? Why not just loop through any time socket() returns -1? The second problem is that even if rsync is compiled with --disable-ipv6, on Linux it still attempts to open an IPv6 socket. This is because the global_opts.af_hint variable is initialized to 0, when it should be initialized to AF_INET to tell getaddrinfo() to prefer IPv4. This brings up a disadvantage with the new global_opts way of specifying global variables; by default the whole structure is now initialized to zero and there's no easy way to s...

Hi All, I'm working on Xen 3.0.2 installation upon Debian 4.1.1-13(kernel 2.6.17.13) Although I spent 2 days to set up Xen 3.0.2, it is failed to install Xen 3.0.2 with several installation manuals which I got from google. I think several trials of Xen installation made my debian system dependancy broken, so when I tried to remove xen-utils package from Debian, it made some errors as

Hi I use the ci_reporter gem for builds on my CI machine (hudson). Prior to rspec 2.4, environment options would override commandline options. So the gem used this to change the formatter and require its files. In 2.4, that order has been reversed. the thing is 2.4 supports multiple formatters, so there is another suggestion. RSpec::Core::ConfigurationOptions def parse_options

On 14 Dec 2001, dwd@samba.org wrote: > open_socket_in was attempting to try all the protocols returned from > getaddrinfo(), but only if a corresponding call to socket() returned one of > three *NOSUPPORT errno codes. A Redhat 6.2 system was observed returning > EINVAL instead so it never went on to try IPv4. This update adds EINVAL to > the list. Question: why not always

Dear all, I''ve just started using puppet-haproxy module and planing to role it out department-wide, so that other group/team/project also can make use it as a core-module. As the several other groups are involved, their requirements are also different. I have two Qs here: How do I customize the "Listen" and "default" section without modifying the actual listen.pp

G''day. I am wondering what the current best practice for building a single file out of distributed fragments is with puppet. Specifically, my problem: 1. Install munin-node on arbitrary machines. 2. Install ''munin.conf'' as a single file on one machine, containing a configuration stanza for every machine that munin-node is installed on. The current best practice