similar to: mod_whatkilledus on Centos 5

I've got a couple of Samba4 DCs running as VMs for testing. The primary AD DC went smoothly. The second VM joined properly and all but it's only when I get to the replication tests that I see errors. This is following the wiki When I run the command "samba-tool drs kcc -Uadministrator windowsdc.mycrap.cnpapers.dom" I get an error indicating that

I'm still not seeing emails from the list. With help from others, I thought I had the IPs cleared since the change back in February, but apparently not. Can someone PM me and let me know what outgoing IP addresses the list is using please? steve campbell

Sorry for the extra info required, but I had digest mode turned on and wouldn't have received the mailing till tomorrow. I have since updated the data manually, but after 'yum update tzdata' was run, the zdump -v for EST5EDT and America/New_York all still showed a date of April 1, instead of March 11. After manually fixing, it is correct. This was mostly a question about why yum

I'm running my AD now, but testing some things dependent on DNS does not seem to be working. Our server is setup in our cnpapers.net domain and was provisioned using Internal Samba DNS. The forwarder is set properly, and almost everything resolves. The forwarder DNS server only has a subset of zones we use on it and it forwards requests to our public/real DNS server. So a request would

I checked my settings on the dovecot mailman page, and although my account was set to "disable" email, after changing it and attempting to have the list resend my password, I'm still not seeing emails. The last time I received emails, the outgoing server for the list was sent from the IP 193.210.130.67. Is that still correct? I've checked my logs to see if there's

I read a few days back on the list where the tzdata rpm was to take care of the new DST rules. I run CentOS 3 servers, and did a 'yum update tzdata' , but received a 2006a update of the rpm. Is this proper? It sure didn't fix anything. Thanks Steve Campbell campbell at cnpapers.com Charleston Newspapers

I'm sure these sound like stupid questions, or have really simple answers, so sorry. The really bad thing is I originally sent these to samba-bounces. Oops. Once we get this Samba AD thing installed, we'd like to have users login and mount particular shares to drive letters based on their group, not their user. All I've read about this seems to use "user" scripts (along

Still new to dovecot, I'm seeing a couple of errors in my log file indicating corruption of index files. Error: Corrupted index cache file/home/xxxxxx/mail/.imap/sent-mail/dovecot.index.cache: Broken virtual size for mail UID 67: 1 Time(s) Error: FETCH [] for mailbox ~/mail/sent-mail UID 67 got too little data: 6203 vs 7478: 1 Time(s) This account is used by multiple users, but it is not

I've got a Centos 5 server with Xen installed. I'm trying to install a Centos 6.5 VM on it but once all is installed, the X window will not sync or display. I think I understand that it's probably due to the settings on the vnc stuff. I've got Centos 6.2 VMs that act just fine. Is there a way I can modify the VM's screen settings either during installation or after

I just upgraded one of my Tao boxes to Centos 3. The usual procedure is to do a yum update twice, and all is fine. This time, I had to rebuilddb before I could run the second yum update, and once I started this, yum fails. It says that $releasever is "1.0". Now I realize I could manually edit my yum.conf and make it go to 3, but this may not fix the problem down the road. Can

Deal developers, I'd like to follow the thread http://www.zytor.com/pipermail/syslinux/2013-April/019761.html but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and provide more test cases. The pxelinux before version 5, e.g. version 4.06, worked very well with memtest86+ 4.20, all my PXE client machines, including VMWare workstation 9, VirtualBox 4.2, and all the real

I'm going to have to be a little vague on this one, but hope I provide enough to make the question clear. I'm not doing the work on this server, a co-worker is, but I said I would ask for him. He is trying to get DRBD installed. He's using Centos 5.1 and the yum repos, but is getting problems with things like the kernel, drbd.so, and the likes. All install fine, but I'm not

I've just spent at least half an hour swapping files, downloading things and stuffing around with memtest86 and memtest86+. I can't get either to start from pxelinux. Currently I have "memtest86" as the filename, and i'm trying to load it direct (not trying to use memdisk or anything). This just results in a near instant reboot. Am I doing something wrong? I can't

We have a situation here that is a real mystery. Our MRTG on our outgoing router and a firewall server that protects our web servers is showing a spike every six hours. I can't find the server behind the firewall that is generating such an extreme amount of packets, even though I've looked through the crontabs of nearly all servers, performed "ps" variations, and other

Hi there, ----- Original Message ----- From: koxudaxi at gmail.com To: syslinux at zytor.com Date: 01.04.2013 10:00:27 Subject: Re: [syslinux] Problem with pxelinux 5.0 and memtest > On 04/01/2013 09:28 AM, H. Peter Anvin wrote: >> On 03/31/2013 05:26 PM, Koudai Aono wrote: >>> I ran the test on a x86 emulator is called Oracle VirtualBox. >>> I think it might not be

On Thu, Sep 12, 2013 at 12:24 AM, Steven Shiau <steven at nchc.org.tw> wrote: > On 2013/9/12 11:55, Steven Shiau wrote: >> >> Deal developers, >> I'd like to follow the thread >> http://www.zytor.com/pipermail/syslinux/2013-April/019761.html >> but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and >> provide more test cases.

On Fri, 2018-07-20 at 10:10 -0500, Michael Hennebry wrote: > On Tue, 17 Jul 2018, Pete Biggs wrote: > > > Check your hardware - all these things might well be symptomatic of an > > hardware issue. > > I'm not at all sure how. > If it means opening the case, > hardware issues are likely to occur. > > Is there a way to tell whether the video > player is

On Thu, Feb 2, 2017 at 1:26 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Hi all, > > > > I have observed a problem where, under legacy BIOS booting mode on the > > DL360g9, memdisk fails to execute. The same mechanism works fine on the > > DL360g8. The system displays the below on the console and ceases to > > respond and must be

El lun, 23-10-2006 a las 16:28 +0400, Kirill Korotaev escribi?: > J.J.Garcia, > > in july 2006 you reported hit of bio.c:99 bug on CentOs kernel: > http://lists.centos.org/pipermail/centos/2006-July/067539.html > > Recently, we also hit the same bug, so maybe you can provide some details on: > 1. whether it is doesn't work for you or was fixed. > 2. how it was

I know how to use 'ip' to set up a static route, e.g.: ip route add 192.168.128.0/17 via 40.53.24.3 dev eth0 But if you reboot or restart network, you loose this. Thus you have to make it persistant. I found: http://www.cyberciti.biz/tips/configuring-static-routes-in-debian-or-red-hat-linux-systems.html where it says to add to ifcfg-eth0: 192.168.128.0/17 via 40.53.24.3 But this