similar to: Hostname resolve fails after upgrade from 4.2 to 4.5

On Thursday, 11 May 2017 21:11:52 CEST Guru Prasad via samba-technical wrote: > If the machine has samba 4.4 or above installed in it then any program such > as ping sends a request to winbindd for name resolution. > > Hope ping is a independent program and doesn't depend on samba or winbindd. > Then how will the ping/mount request reaches winbindd from 4.4 and not > before

(a bit off-topic for samba-technical so I removed that CC) The short answer would be to read the nsswitch.conf manpage - you need libnss_wins.so in /lib and you need "wins" in the "hosts" line in /etc/nsswitch.conf. I found this description in the wiki, which tries to explain how this works (pretty much what I've written):

On 05/11/2017 09:33 PM, Guru Prasad wrote: > Thank you very much Uri. > It means winbindd handles netbios name resolution from samba 4.4.0. > Just to understand, before samba 4.4.0 under which process this netbios > name resolution was handled? > It was under the process that called getaddrinfo() or any other glibc name resolution routine. Glibc has a plugin mechanism (name

Dear All, I'm guruprasad hegde. I would like to contribute to Xapian through GSOC-2018. Thank you for this wonderful opportunity. My Introduction: I study MSc in Computer science at the University of Saarland. I finished my 4th semester. Some of the courses I took include NLP, Information Retrieval & Data mining, statistical learning. These courses helped me develop the interest in

Hi All, I created a work product page for GSoC evaluation. I plan to add a couple of sections soon (bit more detail on summary, challenges, Test suite speed up work details). Also, Project plan page is not completed yet. Link: https://trac.xapian.org/wiki/GSoC2018/Maths/Work%20Product Please let me know if you have any suggestion regarding this. Regards, Guruprasad -------------- next part

Hi, I plan to propose 'Math Aware search' project. After the literature review on the topic, I found Tangent or MIaS system would be a good start. With that, I studied both of the systems well. I plan to pick Tangent because it performs better. Also, it has a good literature(thesis report and few papers available) and reference code available. I keep the summary of both the system, I

Hai Marco, Few pointers. First, time is in sync? I guess it is, but check it. Second. Guest access enabled on a domain joint PC ? If you really really want that, then enable user guest in the AD also. But better is avoiding Guest access completely. Join the domain, dont allow guest access and configure it correctly, best tip i can give, for the software deploying share. [wpkg] path

i have a 2 x n matrix that is a paired list of connections, i am working with that looks something like: 1 2 1 3 1 5 2 1 2 3 3 1 3 2 4 5 5 1 5 4 for later operations it would be helpful if i could change this into the form of: 1 2 3 5 2 1 3 3 1 2 4 5 5 1 4 the initial list is randomly generated and the max number of times that any one number can appear is previoulsy defined by a limiting

I've just upgraded my DM from samba 4.5 to 4.8, using luois repos (also, debian jessie -> stretch). I'm experimenting some troubles on some shares, seems that both guest access and 'machine account' access does not work. The share is rather simple: [wpkg] browseable = No comment = WPKG Automated Software Deploying System force create mode = 0664 force directory mode =

Xapian 1.4.6 can now be downloaded from: https://xapian.org/download This release includes a fix for CVE-2018-0499: https://trac.xapian.org/wiki/SecurityFixes/2018-07-02 The wiki will shortly have a summary of the most notable changes: https://trac.xapian.org/wiki/ReleaseOverview/1.4.6 A big thanks to the following people for helping to make this release a reality: Germán M. Bravo, Robert

Xapian 1.4.7 can now be downloaded from: https://xapian.org/download This release fixes a regression in Database::check() (and the xapian-check command line tool which calls that method), fixes a cursor rebuild bug in the glass backend, adds four new stemmers, plus a few other changes. The wiki has a summary of the most notable changes: https://trac.xapian.org/wiki/ReleaseOverview/1.4.7 A big

Hi Alasdair, This is dm-ioband v1.12.3 release that is a minor update to avoid sparse warnings other than related to the event tracing. (I used sparse-2009-07-29.) This patch can be applied to the current dm-devel tree and 2.6.31-rc4, so could you please replace dm-add-ioband.patch in your tree with this? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to

Hi Alasdair, This is dm-ioband v1.12.3 release that is a minor update to avoid sparse warnings other than related to the event tracing. (I used sparse-2009-07-29.) This patch can be applied to the current dm-devel tree and 2.6.31-rc4, so could you please replace dm-add-ioband.patch in your tree with this? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to

Hi Alasdair, This is dm-ioband v1.12.3 release that is a minor update to avoid sparse warnings other than related to the event tracing. (I used sparse-2009-07-29.) This patch can be applied to the current dm-devel tree and 2.6.31-rc4, so could you please replace dm-add-ioband.patch in your tree with this? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to

Hi Alasdair, This is dm-ioband v1.12.2 release that is a minor update to fit the current dm-devel tree. Could you please replace dm-add-ioband.patch in your tree with this patch? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to upstream. Thanks, Ryo Tsuruta About dm-ioband: dm-ioband is an I/O bandwidth controller implemented as a device-mapper

Hi Alasdair, This is dm-ioband v1.12.2 release that is a minor update to fit the current dm-devel tree. Could you please replace dm-add-ioband.patch in your tree with this patch? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to upstream. Thanks, Ryo Tsuruta About dm-ioband: dm-ioband is an I/O bandwidth controller implemented as a device-mapper

Hi Alasdair, This is dm-ioband v1.12.2 release that is a minor update to fit the current dm-devel tree. Could you please replace dm-add-ioband.patch in your tree with this patch? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to upstream. Thanks, Ryo Tsuruta About dm-ioband: dm-ioband is an I/O bandwidth controller implemented as a device-mapper

Hi All, This is the dm-ioband version 1.12.0 release. dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. The major change of this release is that a new bandwidth control policy "range-bw" is supported. This policy is developed by Dong-Jae Kang,

Hi All, This is the dm-ioband version 1.12.0 release. dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. The major change of this release is that a new bandwidth control policy "range-bw" is supported. This policy is developed by Dong-Jae Kang,

Hi All, This is the dm-ioband version 1.12.0 release. dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. The major change of this release is that a new bandwidth control policy "range-bw" is supported. This policy is developed by Dong-Jae Kang,