search for: l300

On 25/09/2018 22:39, Stephan Bosch wrote: Hello, > Something mightily weird is going on at your end. It doesn't fail here This is correct. I believe there to be a compiler problem. Removing optimisation from sieve-binary-code.c gives success. Thank you to Stephan Bosch for testing this for me and pointing me in the right direction. My debugging was confused because dovecot flags

...y when Battery Charge/Runtime reaches 0. > Is this correct? Or should there be an earlier transition and shutdown triggered by OB LB? The driver should recognize one of several standard shutdown notifications: https://github.com/networkupstools/nut/blob/v2.7.2-signed/drivers/openups-hid.c#L300-L302 However, I don't know which of these is actually implemented in the firmware. If you can afford some downtime, you can capture a log as the battery discharges - let us know if you want to try that. To synthesize the OB+LB state, you can use the "ignorelb" flag with override.bat...

...chunks" to raw and raw to qcow2) Why not use the offset/size support in the raw driver? We use that to access files inside OVA files (also a tar file with a funny extension) in virt-v2v: https://github.com/libguestfs/libguestfs/blob/994ca8d87361a4eb52a05bb4496b074fc9cb705a/v2v/input_ova.ml#L300 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc....

...te the problem. Ok, good. I'd still like to know whether doing this helps somehow: > Does it help when you change the "> 0" at the following code position > to "!= 0" ? > > https://github.com/dovecot/pigeonhole/blob/master/src/lib-sieve/sieve-binary-code.c#L300 Regards, Stephan.

...aches 0. > > Is this correct? Or should there be an earlier transition and shutdown > triggered by OB LB? > > The driver should recognize one of several standard shutdown notifications: > > https://github.com/networkupstools/nut/blob/v2.7. > 2-signed/drivers/openups-hid.c#L300-L302 > > However, I don't know which of these is actually implemented in the > firmware. If you can afford some downtime, you can capture a log as the > battery discharges - let us know if you want to try that. > > To synthesize the OB+LB state, you can use the "ignorelb&...

Full_Name: Martha Nason Version: 2.0.1 OS: Windows XP Submission from: (NULL) (137.187.154.154) I am running simulations using fisher's test on 2 x c tables and a very small p.value from fisher's test (<2.2e-16) is returned as a negative number. Code follows. > set.seed(0) > nreps.outer <-7 > pvalue.fisher <- rep(NA,nreps.outer) > > population1 <- c(

...h compiler is used anyway? Perhaps different versions for the Dovecot releases that do and don't work? Does it help when you change the "> 0" at the following code position to "!= 0" ? https://github.com/dovecot/pigeonhole/blob/master/src/lib-sieve/sieve-binary-code.c#L300 Regards, Stephan.

Hi all, In a conversation between me, Milind and Csaba, Milind pointed out fadvise(2) [1] and its potential benefits to Glusterfs' caching translators like read-ahead etc. After discussing about it, we agreed that our performance translators can leverage the hints to provide better performance. Now the question is how commonly applications actually provide hints? Is it something that is used

Hi all, I've been doing a ton of embedded work (bare metal ARM Cortex M0+ and M4, hopefully RISCV in the future) in the last year and would love to start using and hacking on the llvm toolchain. I've tried setting up clang + lld but can't get lld to work because clang tries to launch gcc. I realize support is early but I'd love to have a dev setup so I can help fix things. Could

Thanks for your ideas, Sean ! >The bug is not likely to be corrupted data in the decompressed output (that is just calling into a gzip routine or something). You shouldn't have to dump/printf->trace from memory during boot to see that data since the "real" kernel binary that is being decompressed into that memory region is probably already somewhere > in your build tree

Hi Charles, Tim, Ah, thanks for bit about the dependencies. Would have thought them to be version specific. Tried with the client and server debs but it seems too many dependency differences between wheezy and jessie. I also tried upgrading from wheezy to jessie wholesale to see if that worked and it did solve nut but in the process broke something else that's more critical so I'll give

I am also philosophically opposed to changing the specification. That said, there's nothing wrong with adding a note to the specification about the common implementations, particularly the reference library. Then, future developers will know both the precise specification and still have the warning that they risk incompatibility by deviating from the reference implementation. I own devices

On 25/09/2018 22:39, Stephan Bosch wrote: > Something mightily weird is going on at your end. It doesn't fail here > (see below). First of all, what is your configuration (output from > `dovecot -n`)? You have dovecot.conf but... $ dovecot -c dovecot.conf -n # 2.3.3.rc1 (14e4920d8): dovecot.conf # Pigeonhole version 0.5.2 (7704de5e) # OS: SunOS 5.11 i86pc # Hostname: mailhost