similar to: ext3 filesystem corruption

Hi all, I posted on both mailing as this seems to be (to me) an internal issue. As the 4.3.1 went out I decided to switch my DC from 4.3.0 to this new version. The process was to install Samba 4.3.1 on new systems, joining these Samba as DC, seizing FSMO roles, demote all 4.3.0. The few I tested until now is working except for DNS entries: samba_dnsupdate is not working as it tries to update

Hi Toni, I'm sorry, I haven't had much time to work on this today. When I run sshd (from the patched snapshot) in a debugger, with a breakpoint early in setup_sia(), this is what I find after connecting with a client: (1) There are two sshd processes. One is running as root, and the other as the user I logged with using the client. The root process is the one in the debugger,

Hey, Thank you Louis for this script, I didn't yet took time to dig in but I'll do. I didn't took time neither to perform another test. That should be done today. Anyway I waited for DC synchronisation before posting. I joined my DC and removed the old ones almost at same time then I gave more than 12 hours to my DC to synchronize. Then I tried to understand what happened, I wrote

OK, I got a chance to try out the Tru64 patch for privsep. I applied the patch to 3.4p1. Partial success, in that it now works for me for logins to "root". Logins to ordinary accounts fail after authentication, when trying to set tty characteristics. See the excerpt from the debug messages below. This is for Tru64 V4.0F (with enhanced_security turned on, obviously.) I guess it's time

Hi All, About once a week, I get a this strange error on bash command line. Running any command on the command line results in " Input/output error". Only way to get back to normal operation is to hard reboot the machine. I suspect this is something to do with my file system. I am using RH7.3 with ext3 file system on IBM Travelstar drives. I use dd to duplicate the drives. The source

Hi Ole, I'm still not answering your issue but I come back to speak about TTL. Perhaps someone would be able to bring us some light on that. This morning I'm trying to reproduce the way I do broke my test AD domain. This leads me to deal with SOA record (I broke my test AD seizing FSMO roles before removing old FSMO owner, SOA was not changed during that process and I suspect this was

On 11/20/2015 10:17 AM, mathias dufresne wrote: > > > 2015-11-20 15:11 GMT+01:00 James <lingpanda101 at gmail.com > <mailto:lingpanda101 at gmail.com>>: > > On 11/20/2015 7:40 AM, Ole Traupe wrote: > > > > Am 20.11.2015 um 11:54 schrieb mathias dufresne: > > Hi Ole, > > I'm still not answering your issue

Hi All, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady

On 11/20/2015 7:40 AM, Ole Traupe wrote: > > > Am 20.11.2015 um 11:54 schrieb mathias dufresne: >> Hi Ole, >> >> I'm still not answering your issue but I come back to speak about >> TTL. Perhaps someone would be able to bring us some light on that. >> >> This morning I'm trying to reproduce the way I do broke my test AD >> domain. This

Hi guys, I have a problem with powering down my system under the XEN hypervisor. System details are as follows: gentoo linux, X86_64 XEN version 4.2.2 linux hardened kernel 3.9.5 as dom0 Xeon E3 1260L processor (vt-d capable) 32GB ECC RAM which has been thoroughly tested - so should be o.k. when I issue "shutdown -h now" from dom0 the system usually reboots instead of turning off

Hi all, I have what appears to be a truly puzzling problem. I've got this P4 32-bit machine running CentOS 5.5 with XEN that has two NICs: one onboard, an Intel Corporation 82540EM Gigabit and one on an expansion card, Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit. The second one is recognized as eth1. What's happening is, it is showing up under one of the two MAC's: either

Thank you for your response. The point is that I have configured my system to shut down at the event "upsc Inform@localhost ups.status"!="OL", not at "LB". So there will be no /etc/killpower file created. At an ups.status != "OL" event, the following script named "notifyme" is run: echo `date` >> /root/upsLog echo " No power, shutting

Hi all, After installing a bunch of new AD DC using the 4.3.1 version I decided to remove the old ones. On one DC I've set up log level as follow: log level = 1 auth:9 registry:7 winbind:7 passdb:7 sam:3 rpc_srv:2 rpc_cli:2 First I'm not sure this is the right way to declare specific log levels but man smb.conf gives me: Example: log level = 3 passdb:5 auth:10 winbind:2 So it sems, to

As I understand it, the idea behind privsep is to prevent malicious data from the client-side of a connection corrupting a server-side process running as root. To achieve that, it is important that post-auth privilege separation happen, ie, that the sshd process change uid to the (authenticated) user. But it is also true that this very same process can perform root-level work without risk of being

After a full device powerdown via the optimus power switch, we seem to lose the HDMI device completely on power on, this keep track of whether we had a hdmi audio sub function device at power on, and pokes a magic register to make it reappear after the optimus power switch is thrown. This at least works on my NVC4 machine, probably needs testing on a few other laptops with other nvidia GPUs.

Recently, I was able to create a workable Centos 4.4 "Live USB" on my 1G Lexar Firefly pendrive using the steps in http://linux.web.psi.ch/livecd/usbdisk.html. At the moment, it is doing its job, so I probably won't focus too much more on it. One thing that is annoying, although doesn't cause a problem is that on powerdown and reboot, the cd rom drive ejects - of course, there

Tru64 patch will not make it into 3.5 (this is final) due to lack of willing people to test. I have given the Tru64/osf1 community almost a month to test it. And *ONE* person came forward to give me verification. And don't give me shit about "I don't have time." The person who tested it was LEAVING his employer with Tru64. He found time. IT IS YOUR GAWD DAMN PLATFORM. IF

Try ALL:ALL in /etc/hosts.allow temporarily. If that still doesn't work, it's likely something else. If it does, only then screw with creating narrow rules . . . - Tim On November 25, 2016 6:37:02 AM CST, Roger Price <roger at rogerprice.org> wrote: >On Fri, 25 Nov 2016, Jonah Naylor wrote: > >> upsd : ipaddressofclientgoeshere > >If it were me I would write >

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

Hello, I find in shutdown.txt file that before system boot after a power failure, it's better to check powerdown flag to be sure and pausing in the startup script to let the batteries recharge with filesystem. So i want to know which startup script is concerned? For the system or for nut? Thanks to explanation. -------------- next part -------------- An HTML attachment was scrubbed... URL: