The way samba is coded, every time a new smbd gets spawned, it reads the
smb.conf file;
so a change to the smb.conf file will get picked up by any NEW connections
,since each
new connection gets its own smbd. Also you can 'force' current smbd's to
re-read the
smb.conf file by sending a kill -HUP <processid> to the process ids of the
smbds.
Perhaps inetd -c is getting inetd to not only reread its inetd.conf file,
but to 'HUP'
the services under its control... I wasn't aware that inetd did that. My
bad..
Don
-----Original Message-----
From: Jansen, Eric [mailto:[log in to unmask]]
Sent: Monday, July 09, 2001 3:31 PM
To: 'MCCALL,DON (HP-USA,ex1)'; [log in to unmask]
Subject: RE: [HP3000-L] samba unreachable from some pc's and not from
othe rs
Hi Don,
I had the idea it did.
And even better, if you change smb.conf, it will get active automatically
after a certain time.
Eric Jansen
> -----Original Message-----
> From: MCCALL,DON (HP-USA,ex1) [mailto:[log in to unmask]]
> Sent: Monday, July 09, 2001 12:49 PM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] samba unreachable from some pc's and not from
> othe rs
>
>
> Hi Andreas,
> as far as I know, inetd -c only causes the current inetd daemon
> to re-read it's inetd.conf file. It does NOT cause the samba services
> to reread the smb.conf file...
> Don
>
> -----Original Message-----
> From: [log in to unmask] [mailto:[log in to unmask]]
> Sent: Monday, July 09, 2001 12:57 PM
> To: MCCALL,DON (HP-USA,ex1)
> Cc: [log in to unmask]
> Subject: Re: [HP3000-L] samba unreachable from some pc's and not from
> others
>
>
> Well, we run Samba under INETD since this was supported ... and didn't
> encounter problems. It's much eleganter to update samba config by
> inetd.net.sys -c instead of aborting and restarting a job I suppose.
>
> Best regards, Andreas Schmidt, CSC, Germany
>
>
>
>
>
> "MCCALL,DON (HP-USA,ex1)" <[log in to unmask]>@RAVEN.UTC.EDU>
> on 09/07/2001
> 15:04:56
>
> Please respond to "MCCALL,DON (HP-USA,ex1)" <[log in to unmask]>
>
> Sent by: HP-3000 Systems Discussion <[log in to unmask]>
>
>
> To: [log in to unmask]
> cc:
> Subject: Re: [HP3000-L] samba unreachable from some pc's and not from
> others
>
>
> Hello Jansen,
> On MPE/iX I would recommend that you do NOT run samba
> under inetd control; stream the job files instead. I have heard some
> instances where services run under inetd would hang (ftp included,
> sometimes), but I don't have any specifics.
> There is also an issue with Samba/iX where the log files
> would not roll
> over
> in the old 5.5 version. Make sure that in your smb.conf file
> you have log
> level = 0 and log size = 10000, so you don't hit a point
> where samba needs
> to rename the logs, and hangs from that. (That issue is
> fixed in patches
> for Samba/iX for 6.0, 6.5 & 7.0 MPE/iX).
>
> Hope this helps,
> Don
>
> -----Original Message-----
> From: Jansen, Eric [mailto:[log in to unmask]]
> Sent: Monday, July 09, 2001 9:50 AM
> To: [log in to unmask]; [log in to unmask]
> Subject: samba unreachable from some pc's and not from others
>
>
> Hi all,
>
> One of our clients has samba version 1.9.16p9 running on a HP3000 MPE
> system
> with OS 5.5 05 p9 (yes, I know it is an old one but the
> client doesn't want
> to upgrade).
>
> After some time of working fine; sometimes weeks, sometimes
> hours; samba is
> unreachable from some pc's.
> We don't really see a certain scenario in which it happens
> neither do we
> have problems with certain pc's, they differ every time.
>
>
> log.smb error:
> -------------
> Added interface ip=<system ip> bcast=<bcast addr> nmask=<nmask>
> 07/06/01 15:05:12 loaded services
> standard input is not a socket, assuming -D option
> Unsupported Samba/iX 0.7 by [log in to unmask] 4/97
> 07/06/01 15:05:12 staying in job mode on MPE
> bind failed on port 139 socket_addr=0 (Address already in use)
> -------------
>
> I checked the network settings with a CISCO network
> specialist and all was
> fine. We also "sniffered" the traffic to the HP3000 and have seen the
> following errors: "window frozen" and "acknowledgement too long". This
> usually reflects to a time-out. Since pinging the system gave a quick
> response time, the network is fine (right?).
>
> To me it seems that the port 139 got hung up for a reason.
>
> Has anybody experienced the same and what can I do to solve it?
> For now we bounce the inetd.
>
> Thanks in advance for your help.
>
> Kind regards,
>
>
> Eric Jansen
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
