search for: 209,11

...file descriptor in the error log. The following patch fixes this for me. I'm sure there is a better way though. --- dovecot-1.2.beta4/src/master/dict-process.c.orig 2009-03-27 16:44:59.000000000 +0100 +++ dovecot-1.2.beta4/src/master/dict-process.c 2009-03-27 18:59:24.000000000 +0100 @@ -209,11 +209,6 @@ dict_process_destroyed(struct child_proc struct dict_listener *listener = process->listener; dict_process_deinit(process); - if (listener->processes == NULL) { - /* last listener died, create new ones */ - listener->io = io_add(listener->fd, IO_READ, - dict_...

...ta, { int r; uint32_t n; - uint64_t real_size_copy; - - pthread_mutex_lock (&lock); - real_size_copy = real_size; - pthread_mutex_unlock (&lock); + uint64_t real_size_copy = get_real_size (); if (offset < real_size_copy) { if (offset + count <= real_size_copy) @@ -209,11 +210,7 @@ truncate_pwrite (struct nbdkit_next_ops *next_ops, void *nxdata, { int r; uint32_t n; - uint64_t real_size_copy; - - pthread_mutex_lock (&lock); - real_size_copy = real_size; - pthread_mutex_unlock (&lock); + uint64_t real_size_copy = get_real_size (); if (offse...

...how qemu-nbd -L is - implemented. The main difficulty is how to express this through - the API since we can no longer user nbd_can_* and nbd_is_* to - unpack the flags. diff --git a/info/nbdinfo.c b/info/nbdinfo.c index bd3615e..cdff958 100644 --- a/info/nbdinfo.c +++ b/info/nbdinfo.c @@ -209,11 +209,12 @@ main (int argc, char *argv[]) fprintf (stderr, "%s\n", nbd_get_error ()); exit (EXIT_FAILURE); } - /* Disconnect from the server to move the handle into a closed - * state, in case the server serializes further connections. - * But we can ignore...

When attempting to build syslinux in parallel (make -j5), I encountered the following error at the end: rm -f liblpxelinux.a ar cq liblpxelinux.a rawcon.o ./fs/pxe/dhcp_option.o ./fs/pxe/pxe.o ./fs/pxe/tftp.o ./fs/pxe/urlparse.o ./lwip/src/netif/ethernetif.o ./lwip/src/netif/etharp.o ./lwip/src/netif/slipif.o ./lwip/src/netif/ppp/md5.o ./lwip/src/netif/ppp/randm.o ./lwip/src/netif/ppp/chpms.o

Hi All I am experiencing a mail download problem with dovecot's pop3 protocol. We use outlook XP 2002 mail clients and I have setup a mail system with pop accounts on a Fedora 2 installation using dovecot. Some of the clients download email fine but others do not download email and also do not give any error messages. I have enabled the "verbose" options in the

I do have a question about whether patch 2 is right, or whether I've exposed a bigger problem in the truncate (and possibly other) filter, but the rest seem fairly straightforward. Eric Blake (4): server: Check for pthread lock failures truncate: Factor out reading real_size under mutex plugins: Check for mutex failures filters: Check for mutex failures filters/cache/cache.c

...be different .. - * These names are also used by the Haskell bindings. - *) -let java_structs = [ +(* For bindings which want camel case *) +let camel_structs = [ "int_bool", "IntBool"; "lvm_pv", "PV"; "lvm_vg", "VG"; @@ -211,11 +209,11 @@ let java_structs = [ "application", "Application"; ] -let java_name_of_struct typ = - try List.assoc typ java_structs +let camel_name_of_struct typ = + try List.assoc typ camel_structs with Not_found -> failwithf - "java_name_of_struct: no java...

...) return NULL; memset(&inreg, 0, sizeof inreg); + buf = lmalloc(count * diskinfo->bps); + if (!buf) + return NULL; + + dapa = lmalloc(sizeof(*dapa)); + if (!dapa) + goto out; + if (diskinfo->ebios) { dapa->len = sizeof(*dapa); dapa->count = count; @@ -209,11 +227,14 @@ void *disk_read_sectors(const struct disk_info *const diskinfo, uint64_t lba, } if (disk_int13_retry(&inreg, NULL)) - return NULL; + goto out; data = malloc(count * diskinfo->bps); if (data) memcpy(data, buf, count * diskinfo->bps); +out: + lfree...

This replaces 13/13 of my v2 series; and now that it has pretty good testsuite coverage and demonstrable performance improvement to nbdinfo, I'm going ahead and pushing this now. We may still want to add further nbd_opt_* commands for other fine-grained tuning of negotiation, but for now, I think things have stabilized on this end, and I can return to polishing .list_exports on the nbdkit

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

...ng_options[option_index].name, option_index); - exit (EXIT_FAILURE); - } + } else + error (EXIT_FAILURE, 0, + _("unknown long option: %s (%d)"), + long_options[option_index].name, option_index); break; case 'a': @@ -209,11 +196,9 @@ main (int argc, char *argv[]) break; case 'm': - if (sscanf (optarg, "%d", &memsize) != 1) { - fprintf (stderr, _("%s: could not parse memory size '%s'\n"), - guestfs_int_program_name, optarg); - e...

This is an incomplete port to Windows. Currently the server compiles and starts up successfully, but goes into an infinite loop when you connect to it. Nevertheless I think the approach is ready for feedback. This being Windows the changes go quite deep. Rich.

With this patchset I have successfully[1] imported a RHEL 5 guest directly from ESX with the following command line: virt-v2v -ic 'esx://yellow.marston/?no_verify=1' -op transfer RHEL5-64 Login details are stored in ~/.netrc Note that this is the only guest I've tested against. I haven't for example, checked that I haven't broken Xen imports. Matt [1] With the exception of

...AND LINE CONFIGURATION>. =item * @@ -185,7 +185,7 @@ Display help. =item B<--output> OUTPUT Write kickstart to C<OUTPUT>. If not specified, the default is -C<p2v.ks> in the current directory. +F<p2v.ks> in the current directory. =item B<--proxy> URL @@ -209,11 +209,11 @@ The L<virt-p2v(1)> binary which is copied into the kickstart file. =item C<$datadir/issue> -=item C<$datadir/launch-virt-p2v.in> +=item F<$datadir/launch-virt-p2v.in> -=item C<$datadir/p2v.ks.in> +=item F<$datadir/p2v.ks.in> -=item C<$da...

Wherever we had code which did: if (something_bad) { perror (...); exit (EXIT_FAILURE); } replace this with use of the error(3) function: if (something_bad) error (EXIT_FAILURE, errno, ...); The error(3) function is supplied by glibc, or by gnulib on platforms which don't have it, and is much more flexible than perror(3). Since we already use error(3), there seems to be

There's not going to be an easy way to present this patch. It's huge and interconnected. Anyway, what it does is lay the groundwork for a new tool which I'm calling 'virt-customize'. virt-customize is virt-builder, but without the part where it downloads a template from a respository. Just the part where it customizes the template, that is, installing packages, editing