search for: 23am

On Thu, Aug 13, 2015 at 09:21:23AM +0200, Sven Schwedas wrote: > > Depends on your needs. If you don't need samba file/printer sharing > /from/ the member, I'd recommend using SSSD. It's much more stable and > reliable than winbindd. Can't let comments like this pass. sssd does something slightly differ...

On Tue, Aug 25, 2015 at 08:36:14AM +0200, Sven Schwedas wrote: > On 2015-08-24 20:55, Jeremy Allison wrote: > > On Thu, Aug 13, 2015 at 09:21:23AM +0200, Sven Schwedas wrote: > > winbindd is extremely reliable and fully supported by the Samba > > Team, please don't post FUD about Samba components. If you have > > winbindd problems, post bug reports > > I did, months ago, the last bug report is still unanswered by...

On Mon, Jul 29, 2019 at 09:59:23AM -0400, Michael S. Tsirkin wrote: > On Wed, Jul 17, 2019 at 01:30:25PM +0200, Stefano Garzarella wrote: > > This series tries to increase the throughput of virtio-vsock with slight > > changes. > > While I was testing the v2 of this series I discovered an huge use of memory, &gt...

On Mon, Jul 29, 2019 at 09:59:23AM -0400, Michael S. Tsirkin wrote: > On Wed, Jul 17, 2019 at 01:30:25PM +0200, Stefano Garzarella wrote: > > This series tries to increase the throughput of virtio-vsock with slight > > changes. > > While I was testing the v2 of this series I discovered an huge use of memory, &gt...

On Mon, Sep 02, 2019 at 11:57:23AM +0200, Stefano Garzarella wrote: > > > > Assuming we miss nothing and buffers < 4K are broken, > > I think we need to add this to the spec, possibly with > > a feature bit to relax the requirement that all buffers > > are at least 4k in size. > > > >...

On Mon, Sep 02, 2019 at 11:57:23AM +0200, Stefano Garzarella wrote: > > > > Assuming we miss nothing and buffers < 4K are broken, > > I think we need to add this to the spec, possibly with > > a feature bit to relax the requirement that all buffers > > are at least 4k in size. > > > >...

On Wed, Jan 21, 2004 at 08:25:23AM -0800, Robert Mykland wrote: > I'm the guy who is working on the LLVM bytecode documentation. The > document I have at present just supports the bytecodes my code > generator processes, though, which is far from all of them. As I get > farther along with my code generator I expect I...

I'm the guy who is working on the LLVM bytecode documentation. The document I have at present just supports the bytecodes my code generator processes, though, which is far from all of them. As I get farther along with my code generator I expect I'll get to the point where everything kind of fits together for me and I can finish it up. In the meantime, people are welcome to what I have

On Thu, Apr 14, 2016 at 07:38:23AM -0600, Eric Blake wrote: > > + /* Read the umask. */ > > + if (read (fd[0], &mask, sizeof mask) != sizeof mask) { > > + perrorf (g, "read"); > > + close (fd[0]); > > + return -1; > > Oops - this strands a child process. You have to reap...

On Fri, Aug 07, 2020 at 10:38:23AM +0200, Juergen Gross wrote: > -# else > - const unsigned char cpu_iret[1]; > -# endif > }; > > static const struct patch_xxl patch_data_xxl = { > @@ -42,7 +38,6 @@ static const struct patch_xxl patch_data_xxl = { > .irq_save_fl = { 0x9c, 0x58 }, // pushf; pop %[re]ax...

On Fri, Aug 07, 2020 at 10:38:23AM +0200, Juergen Gross wrote: > -# else > - const unsigned char cpu_iret[1]; > -# endif > }; > > static const struct patch_xxl patch_data_xxl = { > @@ -42,7 +38,6 @@ static const struct patch_xxl patch_data_xxl = { > .irq_save_fl = { 0x9c, 0x58 }, // pushf; pop %[re]ax...

On Fri, Aug 02, 2019 at 10:19:49AM -0400, mark wrote: > Fred Smith wrote: > > On Fri, Aug 02, 2019 at 09:28:23AM -0400, mark wrote: > <MVNCH> > > One thing I don't understand is how/why the firewall is DROPping so > > many attempts on port 25 when it in fact has a port forward rule sending > > port 25 on to my mailserver. How does it know, or why does it think that > > som...

On Tue, Jul 09, 2013 at 11:46:23AM +0930, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > For small packets we can simplify xmit processing > > by linearizing buffers with the header: > > most packets seem to have enough head room > > we can use for this purpose....

On Tue, Jul 09, 2013 at 11:46:23AM +0930, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > For small packets we can simplify xmit processing > > by linearizing buffers with the header: > > most packets seem to have enough head room > > we can use for this purpose....

Hello, everybody I use virt to run my VM's and QEMU as a hypervisor. There is a file describing my virtual machine: /etc/libvirt/qemu/centos7.0.xml As you know it contains xml representation of my VM. Is there any way to show underlying qemu command that virsh runs using that file? For example: qemu-system-x86-64 -m 1024 -smp 2 -... If no, is there any way to figure it out during VM run ?

Hi all, My server machine is running samba version 4.4.4 on Linux with 'smb encryption = mandatory' option. My client is a Ubuntu 16.10 Linux machine. I am looking for a way to mount the encrypted samba share on the Linux client machine. I noticed that mount.cifs does not support encryption but smbclient does with an -e flag, however it seems to only be usable in a ftp-like interface.

Resending the refactored patch: I realized after I emailed it that it referenced the wrong bugzilla.

Hello all I tried to enable PCI Passthrough in my Debian Squeeze installation. Unfortunately, it didnt work. The following bug showed up (excerpt from dmesg): [ 10.148612] uhci_hcd 0000:00:14.2: PCI INT D -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11 [ 4.678352] Failed to setup GSI :11, err_code:-22 [ 4.678480] dmfe 0000:00:0e.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low)

hello, I got those extensions: exten => 555,1,MeetMeCount(500|count) exten => 555,2,Gotoif,$[${count} = 1]?6 exten => 555,3,Meetme,500|pMs|1234 exten => 555,4,Playback,goodbye exten => 555,5,Hangup exten => 555,6,Goto(from-internal-custom,556,1) exten => 555,7,hangup exten => 556,1,System(/bin/cp /etc/asterisk/1-test /var/spool/asterisk/outgoing/) exten =>

On Mon, Jul 22, 2019 at 11:44:23AM +0200, Christoph Hellwig wrote: > The parameter is always false, so remove it as well as the -EAGAIN > handling that can only happen for the non-blocking case. ? Did the EAGAIN handling get removed in this patch? > Signed-off-by: Christoph Hellwig <hch at lst.de> > drivers/gpu/...