similar to: docs.gluster.org

Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit?: > Hello, > > To reduce confusion, we've setup docs.gluster.org pointing to > gluster.readthedocs.org. Both URLs will continue to work for the > forseeable > future. > > Please update any references that you control to point to > docs.gluster.org. At > some point in the distant future, we will switch to

Le vendredi 01 septembre 2017 ? 14:02 +0100, Michael Scherer a ?crit?: > Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit?: > > Hello, > > > > To reduce confusion, we've setup docs.gluster.org pointing to > > gluster.readthedocs.org. Both URLs will continue to work for the > > forseeable > > future. > > > > Please update any

On Fri, Sep 1, 2017 at 9:42 AM, Michael Scherer <mscherer at redhat.com> wrote: > Le vendredi 01 septembre 2017 ? 14:02 +0100, Michael Scherer a ?crit : >> Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit : >> > Hello, >> > >> > To reduce confusion, we've setup docs.gluster.org pointing to >> > gluster.readthedocs.org. Both URLs will

On Fri, Sep 01, 2017 at 06:21:38PM -0400, Amye Scavarda wrote: > On Fri, Sep 1, 2017 at 9:42 AM, Michael Scherer <mscherer at redhat.com> wrote: > > Le vendredi 01 septembre 2017 ? 14:02 +0100, Michael Scherer a ?crit : > >> Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit : > >> > Hello, > >> > > >> > To reduce confusion,

Hello folks, I spend some time today mucking about trying to figure out how to make our documentation search a better experience. The short answer is, search kind of works now. Long answer: mkdocs creates a client side file which is used for search. RTD overrides this by referring people to Elasticsearch. However, that doesn't clear out stale entries and we're plagued with a whole lot of

Hello folks, We have discovered that for the last few weeks our mailman server was used for a spam attack. The attacker would make use of the + feature offered by gmail and hotmail. If you send an email to example at hotmail.com, example+foo at hotmail.com, example+bar at hotmail.com, it goes to the same inbox. We were constantly hit with requests to subscribe to a few inboxes. These requests

Le samedi 16 septembre 2017 ? 20:48 +0530, Nigel Babu a ?crit?: > Hello folks, > > We have discovered that for the last few weeks our mailman server was > used > for a spam attack. The attacker would make use of the + feature > offered by > gmail and hotmail. If you send an email to example at hotmail.com, > example+foo at hotmail.com, example+bar at hotmail.com, it goes

Hai, i've seen a core dump... ? Clean server, static ip, Debian Jessie, samba 4.1.13 and cups installed. ? Im leaving the office now, but ill go test tomorrow some more. It happend while logging in on ssh server. pretty basic setup, like on the wiki, and?pam was updated by running pam-auth-update. tomorrow more info if this is not known. ? Nov 13 16:57:03 rtd-printsvr1 winbindd[12690]:??

Hai, ? Im working on my dhcp server + dns setup with samba4.? ? i've exported the?keytabs ? samba-tool domain exportkeytab?/home/krb5.keytab.samba4 ? when i read the contents of this keytab ? ktutil rkt /home/krb5.keytab.samba4 list ?? 1??? 1???????????? RTD-DC1$@INTERNAL.DOMAIN.TLD ?? 2??? 1???????????? RTD-DC1$@INTERNAL.DOMAIN.TLD ?? 3??? 1???????????? RTD-DC1$@INTERNAL.DOMAIN.TLD ??

i found the following also .. Aug 7 08:44:10 rtd-print1 autofs[15991]: Starting automount.... Aug 7 08:48:26 rtd-print1 autofs[16291]: Stopping automount.... Aug 7 08:48:27 rtd-print1 automount[16302]: syntax error in map near [ * server.internal.domain.tld: ] Aug 7 08:48:27 rtd-print1 autofs[16297]: Starting automount.... Aug 7 08:48:46 rtd-print1 rpcbind: rpcbind terminating on signal.

hai, ? I just noticed, after my pc woke up my A record disapearred. of my 64bit windows. ? ? Mar? 5 15:43:13 rtd-dc1 named[3717]: samba_dlz: starting transaction on zone INTERNAL.DOMAIN.TLD Mar? 5 15:43:13 rtd-dc1 named[3717]: client 10.249.250.64#49271: update 'INTERNAL.DOMAIN.TLD/IN' denied Mar? 5 15:43:13 rtd-dc1 named[3717]: samba_dlz: cancelling transaction on zone

i will do so.... thanks Am 25.01.2017 um 08:46 schrieb L.P.H. van Belle via samba: > Still > > Check this line from you named config. > > include "/etc/bind/named.conf.default-zones"; > > This can cause an overlap in the zones, so be carefull with that one. > > > Greetz, > > Louis > > >> -----Oorspronkelijk bericht----- >> Van: samba

Hai,   Seeing : > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: configured writeable > zone '168.192.in-addr.arpa' > Jan 23 14:55:40 samba01 named[3279]: zone local.laurenz.ws/NONE: has no > NS records > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: Failed to configure zone > 'local.laurenz.ws'   Normaly you should see first the local.laurenz.ws

At page http://getting-started-with-xapian.readthedocs.org/en/latest/overview.html#datasets-and-example-code <http://getting-started-with-xapian.readthedocs.org/en/latest/overview.html#datasets-and-example-code>the python examples file, http://xapian.org/docs/examples/python.tgz <http://getting-started-with-xapian.readthedocs.org/en/latest/overview.html#datasets-and-example-code>

On 7/13/2020 2:43 AM, L.P.H. van Belle via samba wrote: > samba-tool dns query rtd-dc1 0.168.192.in-addr.arpa @ ALL -U administrator I overlooked this check string the other day. Ran it just now and got the following: root at dc1:~# samba-tool dns query rtd-dc1 0.168.192.in-addr.arpa @ ALL -U administrator ERROR: Connecting to DNS RPC server rtd-dc1 failed with (3221225524, 'The object

Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c

I found something particularly strange while trying out different things: I started up upsdrvctl, upsd, and upsmon. I then stopped upsdrvctl, and tried starting the usbhid-ups driver a few times. Each time I executed the driver, it indicated an instance was already running, stopped it, and then started it again....which is what it should do. I then added -DDDD to the command....and then it

> On Sep 9, 2015, at 10:12 AM, Rob Groner <rgroner at RTD.com> wrote: > > linux-5048:/home/rtd # ldd /usr/local/ups/bin/usbhid-ups > linux-vdso.so.1 (0x00007fff403fc000) > libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f7c34b56000) The last line seems to indicate that it is the real libusb-0.1, not -compat. What kernel version on openSUSE? --

And now....suddenly, and so far unexplainably....it works again. I did the same as before, installed openSUSE 13.1 from scratch, then installed the libusb* libraries. And now...it works, so far reliably. I'm certain that there is some micro-step I started doing different than last time. For example, I used to install jedit from the command line after install, but I had started installing

hai, ? Just an informational message and below the fixed for the problems..? ? when upgrading a member server with debian jessie with samba 4.1.17? with samba and winbind installed.? ? For me this was on?my print server. ? steps to take. ? setup the apt sources for sernet. ? install the sernet packages. apt-get install sernet-samba sernet-samba-winbind sernet-samba-common sernet-samba-libs