similar to: Configuring Rsync to run without any user input or Cron job.

For some reason my secondary DC loses sync every once in a while. It looks like this in samba-tool drs showrepl: Last attempt @ Thu Nov 19 13:53:09 2015 CET failed, result 5 (WERR_ACCESS_DENIED) 229 consecutive failure(s). Last success @ Wed Nov 18 18:48:07 2015 CET Restarting samba fixes the issue for an unpredictable time. Sometimes hours, sometimes many weeks. So I wrote a script to

Thanks Rowland, for the thoughts. > If you are running Samba4 as an AD DC, you should never start the nmbd > deamon, you should also never start smbd manually. Yes, I could optimize to use /etc/init.d/samba-ad-dc immediately,but in fact this is what /etc/init.d/samba does. The messages with "AD DC daemon" are generated by that script, and it is the failing one. > What

Hi, I'm running Samba 4.0.0 on a RHEL 6.4 machine and have created a simple share with all the default configuration options. I've also created an application (running on the RHEL box) that does the following: - detects a file appearing in the share (using Inotify looking for the IN_CLOSE_WRITE event) - open and fcntl lock the file - do some processing - move the file to somewhere else

On 30/11/15 10:01, Lars Hanke wrote: > For some reason my secondary DC loses sync every once in a while. It > looks like this in samba-tool drs showrepl: > > Last attempt @ Thu Nov 19 13:53:09 2015 CET failed, result 5 > (WERR_ACCESS_DENIED) > 229 consecutive failure(s). > Last success @ Wed Nov 18 18:48:07 2015 CET > > Restarting samba fixes the issue for an

On 30/11/15 12:35, Lars Hanke wrote: > Thanks Rowland, for the thoughts. > > > If you are running Samba4 as an AD DC, you should never start the nmbd > > deamon, you should also never start smbd manually. > > Yes, I could optimize to use /etc/init.d/samba-ad-dc immediately,but > in fact this is what /etc/init.d/samba does. The messages with "AD DC >

> Why bother with all the above, just use samba-ad-dc instead. Yes, I streamlined the script somewhat. Let's see what happens when replication fails next time. > You are going to have to supply more info, is there anything in the logs > when replication fails? > If not, try raising the log level until you do get something. Anything specific I should look for? As said it

I''ve recently got a new modem. In fact, it''s a modem-router with NAT functionality. Before I had a plain modem-modem, and I was able to access my workstation from my remote server using the IP address assigned to me by my ISP. Now however, that IP address only reaches the modem-router and the IP address of my workstation is set by my modem-router to 192.168.0.2 How can I

On Wednesday, June 03, 2015 05:13 PM, Rowland Penny wrote: > On 03/06/15 09:55, Jacky Chan wrote: >> On Wednesday, June 03, 2015 04:47 PM, L.P.H. van Belle wrote: >>> and as extra, >>> Users which want to use the old samba 4.1 winbind on 4.2, need to set. >>> server services = +winbind, -winbindd >> Can anyone tell me the different between 4.1 winbind and

Hi all, using Asterisk 1.8 beta3 installed from scratch I am not able to stop/start/restart Asterisk deamon with /etc/init.d/asterisk stop|start|restart It just happens nothing, no warnings, errors etc. I am running Debian Lenny. Any ideas what is wrong? Thanks, Oliver -------------- next part -------------- An HTML attachment was scrubbed... URL:

> > If you read what I wrote, you will see I said to replace 'winbindd' with > 'winbind'. We are referring to samba 4.2.1, as standard this uses the > separate 'winbindd' daemon instead of the 'winbind' built into the samba > daemon. > I read what I wrote but what I am saying is something different. The problem may lie not in the use of

On Wednesday, June 03, 2015 04:47 PM, L.P.H. van Belle wrote: > and as extra, > Users which want to use the old samba 4.1 winbind on 4.2, need to set. > server services = +winbind, -winbindd Can anyone tell me the different between 4.1 winbind and 4.2 winbindd? Thanks

I am thinking about writing some sort of deamon which signs syslog files with PGP. This should help dedecting unauthorised changes in the syslog files. What I have in mind works as follows: Whenever a new line is added to a syslog file the existing syslog file checked against the privious made signature. If the file passes this test, the new line(s) is/are added. Then a new signature is

> with a samba 4.2.1 AD DC you automatically use the separate 'winbindd' > deamon and the 'winbind' deamon built into the samba daemon should be > ignored. There is no way that I know to 'disable' the winbind built into > samba, but there is a way to turn it on and turn off 'winbindd', which > is the way I suggested. > The Samba 4.2 release

I have not installed the madwifi specific kernel stuff (kdml and hal-kdml) from atrpms. I have installed with wpa rpms. And my Atheros card is working with almost no work on my part (other than runing wpa_supplicant as a deamon). Nice!

Hi, When a brick fails in EC, What is the healing read/write data path? Which processes do the operations? Assume a 2GB file is being healed in 16+4 EC configuration. I was thinking that SHD deamon on failed brick host will read 2GB from network and reconstruct its 100MB chunk and write it on to brick. Is this right?

Hello, I launched guestfsd in my guest with this command : guestfsd* -rv*. When i close the handle the deamon crashes. This is the output i got (Deamon side) : guestfsd: main_loop : new request, len 0x28 fsync /dev/sda /dev/sr0 : No medium found guestfsd : main_loop : proc 282

On Mon, Jun 12, 2017 at 7:30 PM, Langley, Robert <Robert.Langley at ventura.org > wrote: > As far as the peer status (and I now remember seeing this earlier) the > issue appears to be that the host name for gsaov07 is attempting to resolve > over the wrong network for gluster "ent...." and not "stor.local". > So, it may be as simple as removing gsaov07 as a

As far as the peer status (and I now remember seeing this earlier) the issue appears to be that the host name for gsaov07 is attempting to resolve over the wrong network for gluster "ent...." and not "stor.local". So, it may be as simple as removing gsaov07 as a peer, then probing over the correct network. I'll follow up with the Engine log. Sent using OWA for iPhone

I have an office setup with shorewall and when there''s bandwidth problems, I''d like to know who''s hogging my bandwidth and how (port). What would be the best approach to have shorewall show me something like: IP | Port | Bytes In | Bytes Out I have 20 PCs connected via DHCP. I looked at the documentation and thought that accounting may be close, but accounting

On 29/10/15 05:41 AM, Rowland Penny wrote: > On 29/10/15 09:19, Viktor Trojanovic wrote: >> Hi, >> >> In a book I'm reading on Samba4, the author explains that network >> browsing doesn't work for Samba AD DCs "because there is no nmbd >> process". >> >> It's true enough that I can't browse my DC, however, there is an