any chance this will be incorporated as a configurable option in the future?
if not, why not?
----- Original Message -----
From: "Solomon D. Gongola" <sol@mail.adldata.com>
To: "Troy Hakala" <troy@cookpoint.com>
Cc: <samba@samba.org>
Sent: Monday, June 05, 2000 9:00 AM
Subject: Re: nmbd.pid filename is not configurable. why?
> I'm sure there is a better way, but thids should work:
>
> Compile a second version of samba specifying a different base
> directory than the one you are using. i.e. If you currently use
> /usr/local/samba the pid is /usr/local/samba/var/locks/nmbd.pid.
> Creating the second version to use /usr/local2/samba will put the
> file in /usr/local2/samba/var/locks/nmbd.pid.
>
> There may also be a compile option to isolate the var directory, try
> ./configure --help
> in the samba distribution source directory.
>
> Newer samba versions give nmbd a '-l' option to specify a log
basename
> but i don't think it affects the var directory. :-(
>
> sol gongola
> adl data systems inc.
>
> Date: Sat, 3 Jun 2000 12:36:35 -0700
> From: "Troy Hakala" <troy@cookpoint.com>
> To: <samba@samba.org>
> Subject: nmbd.pid filename is not configurable. why?
> Message-ID: <19d401bfcd93$078eaa20$0900a8c0@fummachineworks.com>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_19D1_01BFCD58.5B0084C0"
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_19D1_01BFCD58.5B0084C0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> i am using IP aliasing to serve 2 IP addresses on the same machine. and
> > i want both IPs to be accessible from Windows machines via a NetBIOS
> name. but to do this, I need to run 2 instances of nmbd each using a >
different smb.conf where each only listens on one IP address.
>
> However, nmbd always uses nmbd.pid as the pid file and the second >
instance of nmbd fails to run because it sees that another instance of > nmbd
is already running. and looking at the source for nmbd.c, the name
> > "nmbd" is hardcoded (version 2.0.7, line 804), so it
can't even be > configured at runtime to use another pid file.
>
> this seems like a bug, rather than a missing feature, given that >
smb.conf seems to support this with the "bind interfaces only" and
> "interfaces" directives.
>
>
> ------=_NextPart_000_19D1_01BFCD58.5B0084C0
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
> <HTML><HEAD>
> <META content=3D"text/html; charset=3Diso-8859-1" >
http-equiv=3DContent-Type>
> <META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV>
> <DIV>i am using IP aliasing to serve 2 IP addresses on the same
machine.
> > and i=20
> want both IPs to be accessible from Windows machines via a NetBIOS name.
> > but to=20
> do this, I need to run 2 instances of nmbd each using a different >
smb.conf where=20
> each only listens on one IP address.</DIV>
> <DIV> </DIV>
> <DIV>However, nmbd always uses nmbd.pid as the pid file and the
second > instance=20
> of nmbd fails to run because it sees that another instance of nmbd is >
already=20
> running. and looking at the source for nmbd.c, the name "nmbd" is
> hardcoded=20
> (version 2.0.7, line 804), so it can't even be configured at runtime to
> > use=20
> another pid file.</DIV>
> <DIV> </DIV>
> <DIV>this seems like a bug, rather than a missing feature,
given > that=20
> smb.conf seems to support this with the "bind interfaces only"
and > "interfaces"=20
> directives.</DIV>
> <DIV> </DIV></DIV></BODY></HTML>
>
> ------=_NextPart_000_19D1_01BFCD58.5B0084C0--
>
> --
> Sol Gongola (sol@adldata.com)
> ADL Data Systems Inc
> 20 livingstone ave
> Dobbs Ferry, NY 10522
> phone: 914 591 1800 fax: 914 591 1818
>