Date: Wed, 23 Sep 1998 21:38:54 -0500> From: "Daryl L. Biberdorf" <darylb@superserve.com> > To: samba@sam > Subject: machine name lookups > Message-ID: <3.0.5.32.19980923213854.008144b0@pop.a001.sprintmail.com> > > > We have been looking for a way to notify our users when they > are running low on disk quota, without sending them mail. > WinPopup actually seemed like the best way, so my partner > began looking at feeding quota output into smbclient -M > when quota was getting tight. > > The only problem is that smbclient -M frequently fails to find > the client's host name. The -I parameter will often fix it, but > I am concerned about the -M problem nonetheless. I have a machine > configured to be a WINS server, and all of the lab machines > are DHCP-configured to use that server. What exactly is > the -M parameter looking for? What would I do to address the > problem? > > I asked a question a week or so ago along the same lines (with > no response :( ), regarding why Samba appears to do a reverse > DNS lookup on clients (using gethostbyaddr() in util.c if I > remember right). Why does it need to do this? Our DNS servers > (maintained by another group) were cut off due to a WAN outage > a week or so ago. At that point, EVERYTHING Samba-related > stopped working due to this lookup. Yuck! (I have since > installed a local caching DNS server. Will this prevent > it from happening in the future? I'd still like to know that > a DNS failure won't stop my lab from working.) > > The reason I ask is that all of our lab machines are dynamically > given IP addresses, with a lease period of 2 hours. None of these > machines is in the DNS system, simply because Lab10 could have > different IPs throughout the day. Is there any way to deal with > the lookup problems I mentioned above? > > Thanks in advance. > > Daryl > Daryl Biberdorf darylb@superserve.com > >But hang on...... wont an LMHOSTS file solve your problem? I had the same issue (not finding hosts with smbclient using their netbios names) and as soon as I made an entry in an LMHOSTS file - all was well. This way you wouldnt need any name resolution server. Give it a go and tell me if it works... Cheers, Darren Smith Unix Administrator CUDiv - Olympic Dam ext. 87242
I must object!!!!! killall works fine on some systems (e.g.: Linux) but on Solaris, killall does just that --- it kills ALL processes. At 10:25 AM 9/25/98 +1000, you wrote:>Date: Thu, 24 Sep 1998 14:35:45 +1000 >From: PayPC System Mail Subscriber <spammail@quanta.paypc.com> >To: samba@samba.anu.edu.au >Subject: Re: Start and stop the samba server >Message-ID: <199809240435.OAA11327@quanta.paypc.com> > > >> Is there a good way to stop and restart the samba server... >> for example to have it re read the smb.conf, without rebooting the >> actual pc? >> >> if I should kill a process should I kill them all ??? if so is there an >> efficent way to do this? > >Heheheh, you guys should read your unix command line help. :) The command >you want is: > >killall -HUP smbd > >killall kills (or sends the specified signal) to all exectuables which the >specified name. > >I've never had problems just SIGTERM'ing (no signal specified to >kill/killall) smbd's on "live" sessions. The only problem I'd envisagewould>be with oplocked files (smbstatus is your friend!).... in which case -HUP >would be the preferred technique - though the changes aren't applied to >already-established sessions. It sounds like samba automagically re-reads >its smb.conf anyhow; I excerpt from the current samba man page: > > The configuration file, and any files that it includes, > are automatically reloaded every minute, if they change. > You can force a reload by sending a SIGHUP to the server. > Reloading the configuration file will not affect connec- > tions to any service that is already established. Either > the user will have to disconnect from the service, or smbd > killed and restarted. > >So if you have a "dead time" auto-logout (as I do), the changes will be >picked up eventually. If you wish to force an immediate change, than >SIGTERMing the sessions is the only way (that is, kill/killall without a >specified signal name). > >Ya know, every time I install/radically alter/remove vital system services >from my always-busy intranet server box without having to run for anothercd,>reboot multiple times, or experience any downtime or interruption of service >whatsoever, I thank whatever wisdom resides within me which prodded me into >deep-sixing my NT4 servers. (We also manage to get one box to do what >required two boxes to perform satisfactorily, and then some.). > >=Rob=
Subject: machine name lookups
Darryl,
the world is waiting for a standard way to integrate the DHCP & DNS
servers. I am waiting too. There is NO WAY the DNS server is gonna
know what IP address DHCPS assigned to a specific mahine. The reason the
integration
is difficult because the DNS is of the galactic-scale heritage, while DHCP is
a typical
micro-departmental feature.
Making your network entirely microsoft is the only way out.
In short all your questions will never be answered. You may have to find
workarounds
like you did with the local -cache-DNS server.
Sarma