similar to: Sendmail and the $h (solved)

Hi. I'm seeing some issues where Entourage clients can see new mail, download it (or partially), but won't display the mail in the mailbox list. Mail shows up as having arrived, but never displays. These clients have worked in the past with versions of 0.99, but not in 1.0-test-56. I have dumped the connection traffic and it looks like Entourage aborts the IMAP session before it

A problem here getting winbind traffic to be encrypted using Kerberos. I have set up a test environment with a pair of servers (actually lxc containers): - samba server (ubuntu 16.04, stock samba 4.3.11) - client machine (ubuntu 16.04) joined with "net ads join" and winbind The client machine has the following in /etc/samba/smb.conf: ------- [global] #netbios name = client-ad

Dear developer, This issue may be not related to openssh but I am not sure. So post it here for some luck. The issue is like this:(you can see more formatted description at (https://serverfault.com/questions/878504/can-only-ssh-unidirectional) I have two centos 7.2 server. One machine ip is 10.104.196.18, another machine is 10.240.197.21. I can successfully ssh from 10.104.196.18 to

Is there a centos recommended repository for centos 7 where I can obtain the keychain package? TIA, Pete

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 6 Jan 2011 20:59:08 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=26242 > > Summary: BUG: unable to handle kernel NULL pointer dereference > at (null) > Product: Memory Management >

Hi Everyone, I'm trying to get an asus motherboard to netboot. It has an integrated Nvidia boot agent that's supposed to network boot pxe happily. I've setup the necessary services and environments in tftpd, however, the boot agent is running into trouble requesting files from the tftp server. It always seems to receive File Not Found errors. The filenames are specified properly

I have set up samba 2.2.2 (debian package 2.2.2-2, actually). Files are shared out (though Win98 doesnt like my valid users lines, a task for another day). However, it hits the fan when I try to share out my printer to my win2000 system (note: I can print from the server). Ive been through DIAGNOSIS.txt and the HOWTO collection, which didnt help, unless I missed something. Here are some relevant

On Fri, Jul 14, 2017 at 05:58:18PM +0200, Mike Galbraith wrote: > On Fri, 2017-07-14 at 17:50 +0200, Peter Zijlstra wrote: > > Urgh, is for some mysterious reason the __bug_table section of modules > > ending up in RO memory? > > > > I forever get lost in that link magic :/ > > +1 > > drm.ko >  20

changeset: 8830:fcc833cbaf82 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Mon Feb 13 10:41:23 2006 +0100 summary: Return real error code from Xen /dev/mem, not EAGAIN. x460: x86_32: Status: - dom0 boots fine - xend loads fine - single HVM domain loads fine - Multiple HVM domains load fine - destruction of any HVM domain causes dom0 to reboot Issues affecting

Dear expeRts, Please find attached the .diff for a bug fix in R-devel 62124. format.ftable() fails to format ftable()s correctly which have no row.vars or no col.vars. That should work with the patch (the example code below also runs correctly for all the (new) 'method's). Cheers, Marius --8<---------------cut here---------------start------------->8--- (ft1 <- ftable(Titanic,

On Fri, 2017-07-14 at 17:50 +0200, Peter Zijlstra wrote: > On Fri, Jul 14, 2017 at 03:36:08PM +0200, Mike Galbraith wrote: > > Ok, a network outage gave me time to go hunting.  Indeed it is a bad > > interaction with the tree DRM merged into.  All DRM did was to slip a > > WARN_ON_ONCE() that nouveau triggers into a kernel module where such > > things no longer warn,

+++ Peter Zijlstra [14/07/17 18:10 +0200]: >On Fri, Jul 14, 2017 at 05:58:18PM +0200, Mike Galbraith wrote: >> On Fri, 2017-07-14 at 17:50 +0200, Peter Zijlstra wrote: > >> > Urgh, is for some mysterious reason the __bug_table section of modules >> > ending up in RO memory? >> > >> > I forever get lost in that link magic :/ >> >> +1

On Fri, Jul 14, 2017 at 06:33:01PM +0200, Mike Galbraith wrote: > On Fri, 2017-07-14 at 18:10 +0200, Peter Zijlstra wrote: > > On Fri, Jul 14, 2017 at 05:58:18PM +0200, Mike Galbraith wrote: > > > On Fri, 2017-07-14 at 17:50 +0200, Peter Zijlstra wrote: > > > > > > Urgh, is for some mysterious reason the __bug_table section of modules > > > > ending

On Fri, 2017-07-14 at 18:10 +0200, Peter Zijlstra wrote: > On Fri, Jul 14, 2017 at 05:58:18PM +0200, Mike Galbraith wrote: > > On Fri, 2017-07-14 at 17:50 +0200, Peter Zijlstra wrote: > > > > Urgh, is for some mysterious reason the __bug_table section of modules > > > ending up in RO memory? > > > > > > I forever get lost in that link magic :/ >

On 03/21/2017 01:41 AM, Thomas Schmitt via Syslinux wrote: > Hi, > > i have uploaded a little gz compressed tarball > > http://scdbackup.webframe.org/block_seq.tgz > > containing > > -rwxr-xr-x thomas/thomas 4552 2017-03-21 09:23 block_seq > -rw-r--r-- thomas/thomas 315 2017-03-21 09:22 block_seq.c > > To be unpacked in a suitable directory by > >

Hello everyone, recently I've found something I consider a bug. Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A. Imagine my surprise when I saw that all messages that are being output on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are terminated with 0x0D, 0x0A. Maybe that's standard behaviour of all stderr messages in all Linux

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.1-2 Followup-For: Bug #566012 Just had another crash. I got the output from a serial console. The kernel doesn't say anything though. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00000400 from 00000000:0000ffff to ffffffff:ffffffff. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00000404 from 00000000:00018000 to ffffffff:ffffffff. (XEN)

On 21/11/2016 17:21, Brian Candler wrote: > I'd quite like to be able to fetch a ticket using the keytab I found a solution to that part by using a different form of principal name with "hostname$" root at client-ad:~# kinit -k -t /etc/krb5.keytab 'CLIENT-AD$@AD.EXAMPLE.NET' root at client-ad:~# klist Ticket cache: FILE:/tmp/krb5cc_0 Default principal:

Hi, I wonder if there is specific requirement or restriction for the decoder in order to be consider "Vorbis" compliant (or let's say, to be a "correct" vorbis decoder). I am experimenting with integerized libvorbis and the decoder delivers the audio data as following, (and compare with the floating point version below). $ tail audioout-int.txt 0290670 025e 085c 02cf 0895

Hi Ben, I was looking into some of the LUT-related modesetting issues. I've noticed the following... after I load nouveau, one of my secondary GPUs shows this on first modeset (with drm.debug=4): [ 2368.081307] [drm:drm_helper_probe_single_connector_modes [drm_kms_helper]] [CONNECTOR:44:DVI-I-1] [ 2368.113148] [drm:drm_add_display_info [drm]] non_desktop set to 0 [ 2368.113183]