search for: bitflags

I am running the stock OpenLDAP-servers on a CentOS 6 system. Everything is working just fine, but I am trying to debug connections from a Ubuntu (18.04) system and want to turn on logging in slapd, but although I can get slapd to create a log file, it never actually writes anything. I have these two lines in /etc/openldap/slapd.d/cn=config.ldif: olcLogFile: /var/log/slapd/log olcLogLevel:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a really odd question i hope someone can help mee with. Then i look in the smbpasswd file most of the accounts have an "X" after the hashed password inside the brackets, something like this smbtest10:2228:01FC5A6BE7BC6929AAD3B435B51404EE:0CB6948805F797BF2A82807973B89537: [UX ]:LCT-00000000: The strange thing is if i remove

Hallo everybody, I just created a small patch for oggenc to be able to read and encode wav6-files. This files are of micro$ofts WAVEFORMATEXTENSIBLE format type and can contain multiple channels. a52dec can produce this type of file from ac3 streams. Might be it would be better to teach oggenc to read ac3 streams natively. There is probably a better way to encode low frequency channels

Hi List, so first the basics. I''m running Arch Linux with 3.13-rc2, btrfs-progs 0.20rc1.3-2 from the repo and I''m using a SSD. So I was having kernel panics with my USB 3.0 Gigabit card and was trying to get a panic output. These panics are intermittent and most often happen while using Chromium. Anyway so my system paniced while I was in Chromium. After the reboot Chromium

I haven't had enough time to fully understand the deferred logic in this change. I spotted one problem, see comments inline. On 2019-10-28 4:10 p.m., Jason Gunthorpe wrote: > From: Jason Gunthorpe <jgg at mellanox.com> > > Of the 13 users of mmu_notifiers, 8 of them use only > invalidate_range_start/end() and immediately intersect the > mmu_notifier_range with some kind

After playing with the vorbis code for a while and doing tons of hacks and analysis on it, I've found it to perform very poorly with impulse signals. The MDCT seems to cause lots of spreading, and it seems to result in much worse impulse performance then mp3. What is the current plan on handling this? Will a smart quantizer be able to avoid it? I've been looking at various ways of

This attempts to implement a "virtual I/O" layer which should allow common drivers to be efficiently used across most virtual I/O mechanisms. It will no-doubt need further enhancement. The details of probing the device are left to hypervisor-specific code: it simple constructs the "struct virtio_device" and hands it to the probe function (eg. virtnet_probe() or

This attempts to implement a "virtual I/O" layer which should allow common drivers to be efficiently used across most virtual I/O mechanisms. It will no-doubt need further enhancement. The details of probing the device are left to hypervisor-specific code: it simple constructs the "struct virtio_device" and hands it to the probe function (eg. virtnet_probe() or

This attempts to implement a "virtual I/O" layer which should allow common drivers to be efficiently used across most virtual I/O mechanisms. It will no-doubt need further enhancement. The details of probing the device are left to hypervisor-specific code: it simple constructs the "struct virtio_device" and hands it to the probe function (eg. virtnet_probe() or

From: Rusty Russell <rusty@rustcorp.com.au> Lguest net driver A simple net driver for lguest. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Cc: Jeff Garzik <jeff@garzik.org> Acked-by: James Morris <jmorris@namei.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> --- drivers/net/Makefile | 1

From: Rusty Russell <rusty@rustcorp.com.au> Lguest net driver A simple net driver for lguest. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Cc: Jeff Garzik <jeff@garzik.org> Acked-by: James Morris <jmorris@namei.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> --- drivers/net/Makefile | 1

The Wine development release 1.6-rc1 is now available. This is the first release candidate for the upcoming Wine 1.6. It marks the beginning of the code freeze period. Please give this release a good testing to help us make 1.6 as good as possible. What's new in this release (see below for details): - New implementation of the typelib creation support. - GLSL-based support for fixed

From: Jason Gunthorpe <jgg at mellanox.com> Of the 13 users of mmu_notifiers, 8 of them use only invalidate_range_start/end() and immediately intersect the mmu_notifier_range with some kind of internal list of VAs. 4 use an interval tree (i915_gem, radeon_mn, umem_odp, hfi1). 4 use a linked list of some kind (scif_dma, vhost, gntdev, hmm) And the remaining 5 either don't use

From: Jason Gunthorpe <jgg at mellanox.com> Of the 13 users of mmu_notifiers, 8 of them use only invalidate_range_start/end() and immediately intersect the mmu_notifier_range with some kind of internal list of VAs. 4 use an interval tree (i915_gem, radeon_mn, umem_odp, hfi1). 4 use a linked list of some kind (scif_dma, vhost, gntdev, hmm) And the remaining 5 either don't use

From: David Vrabel <david.vrabel@citrix.com> The high resolution timer code gets notified of step changes to the system time with clock_was_set() or clock_was_set_delayed() calls. If other parts of the kernel require similar notification there is no clear place to hook into. Add a clock_was_set atomic notifier chain (clock_was_set_notifier_list) and call this in place of clock_was_set().

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others