Chris McKeever
2003-May-18 03:36 UTC
[Samba] [RESOLUTION..?] wins support = yes time server = yes
from another post today about a different topic, the reply said that nmd has some issue restarting with a service smb restart in redhat 7.3..which seems to answer my question as to why I have to do it twice... thanks> -----Original Message----- > From: Chris McKeever > Sent: Friday, May 16, 2003 10:35 AM > To: 'John H Terpstra'; _Chris McKeever_ > Cc: samba@lists.samba.org > Subject: RE: [Samba] wins support = yes time server = yes > > > John et al... > > so I have narrowed the issue down to something flakey with my > system, and was wondering if anyone else has diagnosed this: > > occassionally, if I 'service smb restart' then do a nbtstat > -a IP.of.wins.server from windiws I get host not found. I > need to restart the service again and then it returns some > information. Almost like something is hanging. seems clean > on a reboot though. > > Is there something in a log that can key me on this? which > and what line item..thanks! > > > -----Original Message----- > > From: John H Terpstra [mailto:jht@samba.org] > > Sent: Sunday, May 11, 2003 2:47 PM > > To: Chris McKeever > > Cc: samba@lists.samba.org > > Subject: RE: [Samba] wins support = yes time server = yes > > > > > > Chris, > > > > Suggest you read the chapter on Browsing in the following (work in > > progress) document: > > > > http://samba.org/~jht/Samba-HOWTO-Collection.pdf > > > > I will reply to your earlier emails later today. > > > > Cheers, > > John T. > > > > On Sun, 11 May 2003, Chris McKeever wrote: > > > > > until this issue, all the machines were registering great > > with the wins > > > server, and they do get its IP from DHCP (all > > verified)...since playing with > > > this in the am, it has been about an hour and I am not > seeing anyone > > > registering... > > > > > > they are all remote, and I want to just wait and see if they do > > > register....I rebooted a couple and they did register, but > > here is the weird > > > issue... > > > > > > I can ping them OK, but they dont show up in network > neighborhood... > > > > > > > -----Original Message----- > > > > From: John H Terpstra [mailto:jht@samba.org] > > > > Sent: Sunday, May 11, 2003 11:24 AM > > > > To: Chris McKeever > > > > Cc: Chris McKeever; samba@lists.samba.org > > > > Subject: RE: [Samba] wins support = yes time server = yes > > > > > > > > > > > > On Sun, 11 May 2003, Chris McKeever wrote: > > > > > > > > > yeah..that was a typo--- I did change it to workgroup = > > pruprefcom > > > > > > > > > > now, i just noticed something new... > > > > > > > > > > I restarted without the time server and when I can > > > > > nbtstat -A ip.of.wins.server I recieved the host not found > > > > (the symptom I > > > > > got after starting the time server) > > > > > > > > > > I needed to restart samba again, so something is funky... > > > > > > > > > > So in all infinite IT wisdom, i rebooted and am now seeing > > > > how things are > > > > > going. > > > > > > > > > > quick question - on a windows network, how longs do windows > > > > machines take to > > > > > sync back with the wins server? and then start to show up > > > > in network > > > > > neighborhood?? right now it is seeming to take a long time > > > > > > > > If you blew away your wins.dat file then each machine needs > > > > to re-register > > > > (that takes at least 15 minutes. It is quicker to reboot > > MS Windows > > > > machines as they always register on start up. > > > > > > > > This raises another point, make sure that your MS Windows > > > > clients all have > > > > th IP address of your Samba server in the WINS server > > entries - please > > > > check this. > > > > > > > > In the absence of WINS it can take up to 45 minutes for the > > > > browse list to > > > > stabilize. With WINS it should be stable immediately. > > > > > > > > - John T. > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: John H Terpstra [mailto:jht@samba.org] > > > > > > Sent: Sunday, May 11, 2003 11:13 AM > > > > > > To: Chris McKeever > > > > > > Cc: Chris McKeever; samba@lists.samba.org > > > > > > Subject: RE: [Samba] wins support = yes time server = yes > > > > > > > > > > > > > > > > > > Chris, > > > > > > > > > > > > Many sites run Samba as a WINS server and a time server at > > > > > > the same tme > > > > > > without problem. We need to find out what is causing the > > > > > > problem at your > > > > > > end. > > > > > > > > > > > > On Sun, 11 May 2003, Chris McKeever wrote: > > > > > > > > > > > > > I changed the workgroup to: > > > > > > > > > > > > > > workgroup = prupref.com > > > > > > > > > > > > Doh! This is what you had, isn't it? Is this a typo? > > > > > > > > > > > > Also, I should have asked you to delete the browse.dat and > > > > > > wins.dat files > > > > > > before restarting nmbd and smbd. > > > > > > > > > > > > I will check into this further later today and will get > > > > back to you. > > > > > > > > > > > > - John T. > > > > > > > > > > > > > > > > > > > > and then uncommented the time server = yes > > > > > > > > > > > > > > when running nbtstat -A ip.of.wins.server I get > > host not found > > > > > > > when I commented back out time server I get a > response from > > > > > > the wins server > > > > > > > after issuing: nbtstat -A ip.of.wins.server (with > workgroup > > > > > > = prupref.com OR > > > > > > > workgroup = pruprefcom) > > > > > > > > > > > > > > If someone could turn on thier time server = yes > and see if > > > > > > they get similar > > > > > > > results that would be great. > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: John H Terpstra [mailto:jht@samba.org] > > > > > > > > Sent: Saturday, May 10, 2003 11:40 PM > > > > > > > > To: Chris McKeever > > > > > > > > Cc: Chris McKeever; samba@lists.samba.org > > > > > > > > Subject: RE: [Samba] wins support = yes time > server = yes > > > > > > > > > > > > > > > > > > > > > > > > On Sat, 10 May 2003, Chris McKeever wrote: > > > > > > > > > > > > > > > > > as it is in production, comments and all > > > > > > > > > when I turn the time server on, wins poops out > > > > > > > > > > > > > > > > There is no connection between WINS serving and > > Time Serving > > > > > > > > have nothing > > > > > > > > to do with each other with the only exception > > that it causes > > > > > > > > nmbd (which > > > > > > > > is the WINS server _and_ the NetBIOS Name Server) to > > > > > > > > advertise your server > > > > > > > > as a time server. > > > > > > > > > > > > > > > > I suspect that the real problem you are seeing is caused > > > > > > by the use of > > > > > > > > your internet domain name as a NetBIOS > > workgroup/domain name. > > > > > > > > That is NOT > > > > > > > > a good idea. > > > > > > > > > > > > > > > > Suggest you try changing: > > > > > > > > > > > > > > > > workgroup = prupref.com > > > > > > > > to: > > > > > > > > workgroup = pruprefcom > > > > > > > > > > > > > > > > ie: No '.' or '_' characters in the workgroup name. > > > > > > > > > > > > > > > > Please let me know if this solves the problem. > > > > > > > > > > > > > > > > Cheers, > > > > > > > > John T. > > > > > > > > > > > > > > > > > > > > > > > > > > thanks! > > > > > > > > > > > > > > > > > > # This is the main Samba configuration file. You > > > > should read the > > > > > > > > > # smb.conf(5) manual page in order to understand the > > > > > > options listed > > > > > > > > > # here. Samba has a huge number of > configurable options > > > > > > (perhaps too > > > > > > > > > # many!) most of which are not shown in this example > > > > > > > > > # > > > > > > > > > # Any line which starts with a ; (semi-colon) > > or a # (hash) > > > > > > > > > # is a comment and is ignored. In this example we > > > > will use a # > > > > > > > > > # for commentry and a ; for parts of the config > > > > file that you > > > > > > > > > # may wish to enable > > > > > > > > > # > > > > > > > > > # NOTE: Whenever you modify this file you > should run the > > > > > > > > command "testparm" > > > > > > > > > # to check that you have not made any basic > > > > syntactic errors. > > > > > > > > > # > > > > > > > > > #======================= Global Settings > > > > > > > > > ====================================> > > > > > > > > [global] > > > > > > > > > > > > > > > > > > # workgroup = NT-Domain-Name or Workgroup-Name > > > > > > > > > workgroup = prupref.com > > > > > > > > > > > > > > > > > > # server string is the equivalent of the NT > > > > Description field > > > > > > > > > server string = Directory Server (LDAP) > > > > > > > > > > > > > > > > > > # This option is important for security. It allows you > > > > > > to restrict > > > > > > > > > # connections to machines which are on your local > > > > network. The > > > > > > > > > # following example restricts access to two C class > > > > networks and > > > > > > > > > # the "loopback" interface. For more examples of > > > > the syntax see > > > > > > > > > # the smb.conf man page > > > > > > > > > ; hosts allow = 192.168.1. 192.168.2. 127. > > > > > > > > > > > > > > > > > > # if you want to automatically load your > > printer list rather > > > > > > > > > # than setting them up individually then you'll > > need this > > > > > > > > > # printcap name = /etc/printcap > > > > > > > > > # load printers = yes > > > > > > > > > > > > > > > > > > # It should not be necessary to spell out the > > print system > > > > > > > > type unless > > > > > > > > > # yours is non-standard. Currently supported print > > > > > > systems include: > > > > > > > > > # bsd, sysv, plp, lprng, aix, hpux, qnx > > > > > > > > > ; printing = bsd > > > > > > > > > > > > > > > > > > # Uncomment this if you want a guest account, you must > > > > > > add this to > > > > > > > > > /etc/passwd > > > > > > > > > # otherwise the user "nobody" is used > > > > > > > > > ; guest account = pcguest > > > > > > > > > > > > > > > > > > # this tells Samba to use a separate log file for > > > > each machine > > > > > > > > > # that connects > > > > > > > > > log file = /var/log/samba/log.%m > > > > > > > > > > > > > > > > > > # Put a capping on the size of the log files (in Kb). > > > > > > > > > max log size = 50 > > > > > > > > > > > > > > > > > > # Security mode. Most people will want user level > > > > security. See > > > > > > > > > # security_level.txt for details. > > > > > > > > > security = user > > > > > > > > > # Use password server option only with > security = server > > > > > > > > > ; password server = <NT-Server-Name> > > > > > > > > > > > > > > > > > > # Password Level allows matching of _n_ > > characters of the > > > > > > > > password for > > > > > > > > > # all combinations of upper and lower case. > > > > > > > > > ; password level = 8 > > > > > > > > > ; username level = 8 > > > > > > > > > > > > > > > > > > # You may wish to use password encryption. Please read > > > > > > > > > # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba > > > > > > > > documentation. > > > > > > > > > # Do not enable this option unless you have read > > > > those documents > > > > > > > > > encrypt passwords = yes > > > > > > > > > ; smb passwd file = /etc/samba/smbpasswd > > > > > > > > > > > > > > > > > > # The following are needed to allow password > > changing from > > > > > > > > Windows to > > > > > > > > > # update the Linux sytsem password also. > > > > > > > > > # NOTE: Use these with 'encrypt passwords' and > > 'smb passwd > > > > > > > > file' above. > > > > > > > > > # NOTE2: You do NOT need these to allow > workstations to > > > > > > change only > > > > > > > > > # the encrypted SMB passwords. They allow the > > > > > > Unix password > > > > > > > > > # to be kept in sync with the SMB password. > > > > > > > > > ; unix password sync = Yes > > > > > > > > > ; passwd program = /usr/bin/passwd %u > > > > > > > > > ; passwd chat = *New*UNIX*password* %n\n > > > > > > > > *ReType*new*UNIX*password* %n\n > > > > > > > > > > *passwd:*all*authentication*tokens*updated*successfully* > > > > > > > > > > > > > > > > > > # Unix users can map to different SMB User names > > > > > > > > > ; username map = /etc/samba/smbusers > > > > > > > > > > > > > > > > > > # Using the following line enables you to > customise your > > > > > > > > configuration > > > > > > > > > # on a per machine basis. The %m gets > replaced with the > > > > > > netbios name > > > > > > > > > # of the machine that is connecting > > > > > > > > > ; include = /etc/samba/smb.conf.%m > > > > > > > > > > > > > > > > > > # Most people will find that this option gives better > > > > > > performance. > > > > > > > > > # See speed.txt and the manual pages for details > > > > > > > > > socket options = TCP_NODELAY SO_RCVBUF=8192 > > > > SO_SNDBUF=8192 > > > > > > > > > > > > > > > > > > # Configure Samba to use multiple interfaces > > > > > > > > > # If you have multiple network interfaces > then you must > > > > > > list them > > > > > > > > > # here. See the man page for details. > > > > > > > > > ; interfaces = 192.168.12.2/24 192.168.13.2/24 > > > > > > > > > > > > > > > > > > # Configure remote browse list synchronisation here > > > > > > > > > # request announcement to, or browse list sync from: > > > > > > > > > # a specific host or from / to a whole > > subnet (see below) > > > > > > > > > ; remote browse sync = 192.168.3.25 192.168.5.255 > > > > > > > > > # Cause this host to announce itself to local > > subnets here > > > > > > > > > ; remote announce = 192.168.1.255 192.168.2.44 > > > > > > > > > > > > > > > > > > # Browser Control Options: > > > > > > > > > # set local master to no if you don't want Samba to > > > > > > become a master > > > > > > > > > # browser on your network. Otherwise the normal > > > > > > election rules apply > > > > > > > > > ; local master = no > > > > > > > > > > > > > > > > > > # OS Level determines the precedence of this server in > > > > > > > > master browser > > > > > > > > > # elections. The default value should be reasonable > > > > > > > > > ; os level = 33 > > > > > > > > > > > > > > > > > > # Domain Master specifies Samba to be the > Domain Master > > > > > > > > Browser. This > > > > > > > > > # allows Samba to collate browse lists > between subnets. > > > > > > > > Don't use this > > > > > > > > > # if you already have a Windows NT domain controller > > > > > > doing this job > > > > > > > > > ; domain master = yes > > > > > > > > > > > > > > > > > > # Preferred Master causes Samba to force a > local browser > > > > > > > > election on startup > > > > > > > > > # and gives it a slightly higher chance of winning > > > > the election > > > > > > > > > ; preferred master = yes > > > > > > > > > > > > > > > > > > # Use only if you have an NT server on your network > > > > > > that has been > > > > > > > > > # configured at install time to be a primary domain > > > > controller. > > > > > > > > > ; domain controller = <NT-Domain-Controller-SMBName> > > > > > > > > > > > > > > > > > > # Enable this if you want Samba to be a domain > > > > logon server for > > > > > > > > > # Windows95 workstations. > > > > > > > > > ; domain logons = yes > > > > > > > > > > > > > > > > > > # if you enable domain logons then you may want a > > > > per-machine or > > > > > > > > > # per user logon script > > > > > > > > > # run a specific logon batch file per > > workstation (machine) > > > > > > > > > ; logon script = %m.bat > > > > > > > > > # run a specific logon batch file per username > > > > > > > > > ; logon script = %U.bat > > > > > > > > > > > > > > > > > > # Where to store roving profiles (only for > > Win95 and WinNT) > > > > > > > > > # %L substitutes for this servers > > netbios name, %U > > > > > > > > is username > > > > > > > > > # You must uncomment the [Profiles] share below > > > > > > > > > ; logon path = \\%L\Profiles\%U > > > > > > > > > > > > > > > > > > # All NetBIOS names must be resolved to IP Addresses > > > > > > > > > # 'Name Resolve Order' allows the named resolution > > > > > > > > mechanism to be specified > > > > > > > > > # the default order is "host lmhosts wins > bcast". "host" > > > > > > > > means use the unix > > > > > > > > > # system gethostbyname() function call that > > will use either > > > > > > > > /etc/hosts OR > > > > > > > > > # DNS or NIS depending on the settings of > > /etc/host.config, > > > > > > > > > /etc/nsswitch.conf > > > > > > > > > # and the /etc/resolv.conf file. "host" > > therefore is system > > > > > > > > configuration > > > > > > > > > # dependant. This parameter is most often of > > use to prevent > > > > > > > > DNS lookups > > > > > > > > > # in order to resolve NetBIOS names to IP Addresses. > > > > > > Use with care! > > > > > > > > > # The example below excludes use of name > resolution for > > > > > > > > machines that are > > > > > > > > > NOT > > > > > > > > > # on the local network segment > > > > > > > > > # - OR - are not deliberately to be known via lmhosts > > > > > > or via WINS. > > > > > > > > > ; name resolve order = wins lmhosts bcast > > > > > > > > > > > > > > > > > > # Windows Internet Name Serving Support Section: > > > > > > > > > # WINS Support - Tells the NMBD component of Samba to > > > > > > > > enable it's WINS > > > > > > > > > Server > > > > > > > > > wins support = yes > > > > > > > > > > > > > > > > > > ; time server = yes > > > > > > > > > > > > > > > > > > # WINS Server - Tells the NMBD components of > > Samba to be a > > > > > > > > WINS Client > > > > > > > > > # Note: Samba can be either a WINS > > Server, or a WINS > > > > > > > > Client, but NOT > > > > > > > > > both > > > > > > > > > # wins server = 192.168.2.10 > > > > > > > > > > > > > > > > > > # WINS Proxy - Tells Samba to answer name > > > > resolution queries on > > > > > > > > > # behalf of a non WINS capable client, for > this to work > > > > > > > > there must be > > > > > > > > > # at least one WINS Server on the network. The > > > > default is NO. > > > > > > > > > ; wins proxy = yes > > > > > > > > > > > > > > > > > > # DNS Proxy - tells Samba whether or not to try > > to resolve > > > > > > > > NetBIOS names > > > > > > > > > # via DNS nslookups. The built-in default for versions > > > > > > > > 1.9.17 is yes, > > > > > > > > > # this has been changed in version 1.9.18 to no. > > > > > > > > > dns proxy = no > > > > > > > > > > > > > > > > > > # Case Preservation can be handy - system > > default is _no_ > > > > > > > > > # NOTE: These can be set on a per share basis > > > > > > > > > ; preserve case = no > > > > > > > > > ; short preserve case = no > > > > > > > > > # Default case is normally upper case for all > DOS files > > > > > > > > > ; default case = lower > > > > > > > > > # Be very careful with case sensitivity - it can > > > > break things! > > > > > > > > > ; case sensitive = no > > > > > > > > > > > > > > > > > > ldap admin dn = cn=root,dc=prupref,dc=com > > > > > > > > > ldap server = ldap.prupref.com > > > > > > > > > ldap suffix = dc=prupref,dc=com > > > > > > > > > ldap port = 389 > > > > > > > > > ldap ssl = start_tls > > > > > > > > > > > > > > > > > > #============================ Share Definitions > > > > > > > > > =============================> > > > > > > > > > > > > > > > > > [startup$] > > > > > > > > > comment = central station start-up location > > > > > > > > > path = /home/station-startup > > > > > > > > > browseable = no > > > > > > > > > public = yes > > > > > > > > > read only = yes > > > > > > > > > write list = @domain-admins > > > > > > > > > oplocks = no > > > > > > > > > level2 oplocks = no > > > > > > > > > force directory mode = 0775 > > > > > > > > > force create mode = 0660 > > > > > > > > > force group = domain-admins > > > > > > > > > > > > > > > > > > [pcawin$] > > > > > > > > > comment = admin pcaccess shared files > > > > > > > > > path = /home/admin-pcawin > > > > > > > > > browseable = no > > > > > > > > > public = yes > > > > > > > > > writable = yes > > > > > > > > > oplocks = no > > > > > > > > > level2 oplocks = no > > > > > > > > > force directory mode = 0666 > > > > > > > > > force create mode = 0666 > > > > > > > > > > > > > > > > > > [putty] > > > > > > > > > comment = putty.exe location > > > > > > > > > path = /home/putty > > > > > > > > > browseable = yes > > > > > > > > > public = yes > > > > > > > > > read only = yes > > > > > > > > > write list = @domain-admins > > > > > > > > > oplocks = no > > > > > > > > > level2 oplocks = no > > > > > > > > > force directory mode = 0775 > > > > > > > > > force create mode = 0660 > > > > > > > > > force group = domain-admins > > > > > > > > > > > > > > > > > > > > > > > > > > > #[homes] > > > > > > > > > # comment = Home Directories > > > > > > > > > # browseable = no > > > > > > > > > # writable = yes > > > > > > > > > > > > > > > > > > # Un-comment the following and create the netlogon > > > > > > > > directory for Domain > > > > > > > > > Logons > > > > > > > > > ; [netlogon] > > > > > > > > > ; comment = Network Logon Service > > > > > > > > > ; path = /home/netlogon > > > > > > > > > ; guest ok = yes > > > > > > > > > ; writable = no > > > > > > > > > ; share modes = no > > > > > > > > > > > > > > > > > > > > > > > > > > > # Un-comment the following to provide a > specific roving > > > > > > > > profile share > > > > > > > > > # the default is to use the user's home directory > > > > > > > > > ;[Profiles] > > > > > > > > > ; path = /home/profiles > > > > > > > > > ; browseable = no > > > > > > > > > ; guest ok = yes > > > > > > > > > > > > > > > > > > > > > > > > > > > # NOTE: If you have a BSD-style print system there > > > > is no need to > > > > > > > > > # specifically define each individual printer > > > > > > > > > #[printers] > > > > > > > > > # comment = All Printers > > > > > > > > > # path = /var/spool/samba > > > > > > > > > # browseable = no > > > > > > > > > # Set public = yes to allow user 'guest > > account' to print > > > > > > > > > # guest ok = no > > > > > > > > > # writable = no > > > > > > > > > # printable = yes > > > > > > > > > > > > > > > > > > # This one is useful for people to share files > > > > > > > > > ;[tmp] > > > > > > > > > ; comment = Temporary file space > > > > > > > > > ; path = /tmp > > > > > > > > > ; read only = no > > > > > > > > > ; public = yes > > > > > > > > > > > > > > > > > > # A publicly accessible directory, but read > only, except > > > > > > > > for people in > > > > > > > > > # the "staff" group > > > > > > > > > ;[public] > > > > > > > > > ; comment = Public Stuff > > > > > > > > > ; path = /home/samba > > > > > > > > > ; public = yes > > > > > > > > > ; read only = yes > > > > > > > > > ; write list = @staff > > > > > > > > > > > > > > > > > > # Other examples. > > > > > > > > > # > > > > > > > > > # A private printer, usable only by fred. Spool > > data will > > > > > > > > be placed in > > > > > > > > > fred's > > > > > > > > > # home directory. Note that fred must have > write access > > > > > > to the spool > > > > > > > > > directory, > > > > > > > > > # wherever it is. > > > > > > > > > ;[fredsprn] > > > > > > > > > ; comment = Fred's Printer > > > > > > > > > ; valid users = fred > > > > > > > > > ; path = /homes/fred > > > > > > > > > ; printer = freds_printer > > > > > > > > > ; public = no > > > > > > > > > ; writable = no > > > > > > > > > ; printable = yes > > > > > > > > > > > > > > > > > > # A private directory, usable only by fred. > > Note that fred > > > > > > > > requires write > > > > > > > > > # access to the directory. > > > > > > > > > ;[fredsdir] > > > > > > > > > ; comment = Fred's Service > > > > > > > > > ; path = /usr/somewhere/private > > > > > > > > > ; valid users = fred > > > > > > > > > ; public = no > > > > > > > > > ; writable = yes > > > > > > > > > ; printable = no > > > > > > > > > > > > > > > > > > # a service which has a different directory for each > > > > > > > > machine that connects > > > > > > > > > # this allows you to tailor configurations to incoming > > > > > > > > machines. You could > > > > > > > > > # also use the %u option to tailor it by user name. > > > > > > > > > # The %m gets replaced with the machine name that > > > > is connecting. > > > > > > > > > ;[pchome] > > > > > > > > > ; comment = PC Directories > > > > > > > > > ; path = /usr/pc/%m > > > > > > > > > ; public = no > > > > > > > > > ; writable = yes > > > > > > > > > > > > > > > > > > # A publicly accessible directory, read/write > > to all users. > > > > > > > > Note that all > > > > > > > > > files > > > > > > > > > # created in the directory by users will be > owned by the > > > > > > > > default user, so > > > > > > > > > # any user with access can delete any other > > user's files. > > > > > > > > Obviously this > > > > > > > > > # directory must be writable by the default > > user. Another > > > > > > > > user could of > > > > > > > > > course > > > > > > > > > # be specified, in which case all files would > > be owned by > > > > > > > > that user instead. > > > > > > > > > ;[public] > > > > > > > > > ; path = /usr/somewhere/else/public > > > > > > > > > ; public = yes > > > > > > > > > ; only guest = yes > > > > > > > > > ; writable = yes > > > > > > > > > ; printable = no > > > > > > > > > > > > > > > > > > # The following two entries demonstrate how to share a > > > > > > > > directory so that two > > > > > > > > > # users can place files there that will be > owned by the > > > > > > > > specific users. In > > > > > > > > > this > > > > > > > > > # setup, the directory should be writable by > > both users and > > > > > > > > should have the > > > > > > > > > # sticky bit set on it to prevent abuse. > Obviously this > > > > > > > > could be extended to > > > > > > > > > # as many users as required. > > > > > > > > > ;[myshare] > > > > > > > > > ; comment = Mary's and Fred's stuff > > > > > > > > > ; path = /usr/somewhere/shared > > > > > > > > > ; valid users = mary fred > > > > > > > > > ; public = no > > > > > > > > > ; writable = yes > > > > > > > > > ; printable = no > > > > > > > > > ; create mask = 0765 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > From: John H Terpstra [mailto:jht@samba.org] > > > > > > > > > > Sent: Saturday, May 10, 2003 11:10 AM > > > > > > > > > > To: Chris McKeever > > > > > > > > > > Cc: samba@lists.samba.org > > > > > > > > > > Subject: Re: [Samba] wins support = yes time > > server = yes > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, 10 May 2003, Chris McKeever wrote: > > > > > > > > > > > > > > > > > > > > > When I set: > > > > > > > > > > > > > > > > > > > > > > wins support = yes > > > > > > > > > > > time server = yes > > > > > > > > > > > > > > > > > > > > > > my wins service stops working and no computers > > > > show up in > > > > > > > > > > the network > > > > > > > > > > > neighborhood..as soon as I change time > server = no, > > > > > > > > they start to > > > > > > > > > > > re-populate. > > > > > > > > > > > > > > > > > > > > > > I have looked around and havent found a > > > > definitive answer > > > > > > > > > > (apologies if I > > > > > > > > > > > overlooked it)... > > > > > > > > > > > > > > > > > > > > > > but if someone could tell me if this is a > > > > documented issue, > > > > > > > > > > or just me that > > > > > > > > > > > woudl be great > > > > > > > > > > > > > > > > > > > > I can not see anywhere in the source code > > that time server > > > > > > > > > > may affect WINS > > > > > > > > > > operation. > > > > > > > > > > > > > > > > > > > > Send me your smb.conf and I will give you feedback. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - John T. > > > > > > > > > > -- > > > > > > > > > > John H Terpstra > > > > > > > > > > Email: jht@samba.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > John H Terpstra > > > > > > > > Email: jht@samba.org > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > John H Terpstra > > > > > > Email: jht@samba.org > > > > > > > > > > > > > > > > > > > -- > > > > John H Terpstra > > > > Email: jht@samba.org > > > > > > > > > > > -- > > John H Terpstra > > Email: jht@samba.org > > >
Herbert Lewis
2003-May-19 18:13 UTC
[Samba] [RESOLUTION..?] wins support = yes time server = yes
Chris McKeever wrote:> > from another post today about a different topic, the reply said that nmd has > some issue restarting with a service smb restart in redhat 7.3..which seems > to answer my question as to why I have to do it twice... > > thanks >I discovered on IRIX that not all nmbd process will die if you attempt to kill the process group rather than killing the parent process and letting it kill the child process. Killing the process group twice would kill everything so this sounds similar to what you are seeing.