Re: Lost in samba...
Thank you for your answer. I found the problem. The Win98 PC also had an ethernet connection to another network. Even though the ethernet cable was unplugged, the ethernet interface in Win98 still had an IP address, and that was probably causing the problem... After doing an winipcfg and releasing the IP address on that interface, everything worked fine (the PC now appears in the browse.dat list)... This is so weired ! David. On Tuesday 30 April 2002 19:39, Richard Sharpe wrote: On Tue, 30 Apr 2002, David LIBAULT wrote: Hi all, I am still trying to figure out why my Win98 PC connected with a PPP link to my linux box runing samba-2.2.3a doesn't get registered in the browse.dat file. The linux box is setup as a wins server, and domain + local master browser (how could I make it simpler ? ;-)). Is your Win98 system in the same subnet as your Samba server? If not, are you configuing WINS? You can use DHCP on your dial-up server to give Win98 the WINS server addresses if you want, or you can hard-code them. It looks like the only part of the code when the subnet_record list is updated is when a browse packet with command ANN_HostAnnouncement is sent by the host on an SMB datagram (port 138). Registration on port 137 has no influence on the browse list mantained by the linux box, but just on the wins part of it. On the tcpdump I only see - traffic on port 137 (basically name registration) which looks good as I get the right entry in the wins.dat file - traffic on port 138 : a browse packet with command ANN_GetBackupListReq (to which the linux box answers by a GetBackupListResponse) - and then, a TCP connection to port 139 (handled by smbd) to get the browse list. As the Win98 PC never announce itself on port 138, it never gets registered in the browse.dat file. Is it something wrong in the Win98 PC ? What am I missing ? Thank you for your help. David.
script to find undocumented params
I wrote a little perl script to find those params that have no
documentation
I don't know what most of them do
but i'll get cracking on finding out
here's the output:
display charset
hostname lookups
ldap user suffix
add group script
realm
wins partners
addprinter command
unix charset
lock spin time
admin log
inherit acls
add user to group script
ssl ca certfile
winbind enum groups
max packet
unicode
delete user from group script
wtmp directory
packet size
mangling method
alternate permissions
force directory security mode
ads server
paranoid server security
-valid
ssl ca certdir
lock spin count
winbind enum users
use spnego
delete group script
deleteprinter command
ldap machine suffix
ntlm auth
dos charset
here's the script - in case somebody else wants it
#!/usr/bin/perl -w
#reads in the list of parameters from the source
#compares this list to the list of parms documented in the docbook
source
#prints out the names of the parameters that are in need of
documentation
my $doc_file = ./docs/docbook/manpages/smb.conf.5.sgml;
my $source_file = ./source/param/loadparm.c;
my $ln;
my %params;
open(SOURCE, $source_file) ||
die Unable to open $source_file for input: $!\n;
open(DOC, $doc_file) ||
die Unable to open $doc_file for input: $!\n;
while ($ln= SOURCE) {
last if $ln =~ m/^static\ struct\ parm_struct\ parm_table.*/;
} #burn through the preceding lines
while ($ln = SOURCE) {
last if $ln =~ m/^\s*\}\;\s*$/;
#pull in the param names only
next if $ln =~ m/.*P_SEPARATOR.*/;
$ln =~ m/.*\(.*)\.*/;
$params{lc($1)}='not_found'; #not case sensitive
}
close SOURCE;
#now read in the params list from the docs
doclines = DOC;
foreach $ln (grep (/\anchor\ id\=/, doclines)) {
$ln =~ m/^.*\anchor\
id\=\.*\\\s*(?:\.*?\)*\s*(.*?)(?:\s*\(?[S,G]?\)?\s*(\\/term\)?){1}\s*$/;
#print got: $1 from: $ln;
if (exists $params{lc($1)}) {
$params{$1} = 'found';
}
}
foreach (keys %params) {
print $_\n if $params{$_} eq 'not_found';
}
Some people owe me doc updates...
I need smb.conf entries for * admin log * inherit acls * lock spin count * lock spin time * winbind use default domain And yes I could look in the code, but the rule is you add a parameter, you update the docs. Thanks for the help on this. I'm just about to release 2.2.4 as soon as I get the smb.conf man page up to date. cheers, jerry - Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org --http://www.plainjoe.org Sam's Teach Yourself Samba in 24 Hours 2ed. ISBN 0-672-32269-2 --I never saved anything for the swim back. Ethan Hawk in Gattaca--
Re: Some people owe me doc updates...
On Thu, 2 May 2002, Gerald Carter wrote: I need smb.conf entries for * admin log not used in 2.2 right now so it can wait. * inherit acls Still need this one... * lock spin count * lock spin time I've got these 2 * winbind use default domain Still need this one too. jerry
RE: Some people owe me doc updates...
Gerald Carter [mailto:[EMAIL PROTECTED]] writes: I need smb.conf entries for * admin log * inherit acls * lock spin count * lock spin time * winbind use default domain And yes I could look in the code, but the rule is you add a parameter, you update the docs. Thanks for the help on this. I'm just about to release 2.2.4 as soon as I get the smb.conf man page up to date. Suggestion: in the future turn down code changes w/o accompanying documentation changes. Yes, it is a tough stance, and yes, you might lose a few nice features, or a few coders. But I think it more likely that people will accept the new situation and rise to the challenge. Samba is a critical product these days and having such a requirement would simply recognize that fact. In actuality, I think the actual policy would be to simply defer the commit until the author supplies the documentation changes. Over on the perl5-porters list, where I've been working for ~6 months, we have a pretty good record of getting code changes, docu changes, and test case additions or changes all at the same time. Not perfect, but pretty good. Of course, maybe you are doing this already, and because I've been away for a while I didn't notice. If that's the case, ignore this. PG
