From: Zane H. Healy [healyzh@shell1.aracnet.com]
Sent: Wednesday, February 16, 2000 1:54 AM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: Samba frustrations on reboot

Jeff Campbell <jcampbell@ins-msi.com> wrote:
>> The SAMBA_STARTUP.COM seems to just startup the NMBD process.

> As you note above it defines logical names, including SAMBA_ROOT.

Ah, I think you might have just knocked the problem loose!  I'm defining
SAMBA_ROOT and SAMBA_TMPDIR in SYSTARTUP_VMS.COM (this isn't defined in the
SAMBA_STARTUP.COM that I have).

My def in SYSTARTUP_VMS.COM:
$!
$ define/system/exec/nolog SAMBA_ROOT DKA0:[000000.SAMBA]
$ define/system/exec/nolog SAMBA_TMPDIR DKA0:[000000.SAMBA]
$!

What it is now:
$ pipe show logical * | search sys$input SAMBA_ROOT
  "SAMBA_EXE" = "SAMBA_ROOT:[BIN.ALPHA]"
        = "SAMBA_ROOT:[BIN]"
  "SAMBA_ROOT" = "MONK$DKA0:[SAMBA.]"
$ pipe show logical * | search sys$input SAMBA_tmpdir
  "SAMBA_TMPDIR" = "MONK$DKA0:[SAMBA.VAR]"
$ 

It looks to me like I'm incorrectly setting SAMBA_ROOT and SAMBA_TMPDIR. 
Since neither of these look to be set by any of the startup files I've got
it looks like the only way I'm getting them set correctly is by re-running
the install.

Anyway I've changed the def's in SYSTARTUP_VMS.COM to match their current
values.  Now I just need to find time to reboot the system.  Now I'm wishing
I could reboot it remotely.

				Zane