[Info-vax] DECwindows no longer starting on satellite
Wilm Boerhout
wboerhout-deletethis at gmail.com
Sun Nov 14 16:15:54 EST 2010
smithfarm mentioned on 14-11-2010 20:10:
> Seeing as there appear to be three license databases:
>
>> $ dir dua0:[000000...]lmf$license*.*
>>
>> Directory DUA0:[SYS0.SYSCOMMON.SYSEXE]
>>
>> LMF$LICENSE.LDB;1
>>
>> Total of 1 file.
>>
>> Directory DUA0:[SYS10.SYSCOMMON.SYSEXE]
>>
>> LMF$LICENSE.LDB;1
>>
>> Total of 1 file.
>>
>> Directory DUA0:[VMS$COMMON.SYSEXE]
>>
>> LMF$LICENSE.LDB;1
>>
>> Total of 1 file.
>>
>> Grand total of 3 directories, 3 files.
>
> Could it be that when one node starts up and runs the LICENSE MODIFY and
> LICENSE LOAD commands, it (re)writes to the common license database
> instead of the node-specific one? That might explain why the problem is
> intermittent.
>
> Could it be that all three of the files listed by the above directory
> command are a single file? That would explain it - when I reboot PEAR,
> it modifies the VAX-VMS license to be for PEAR only. Then, when I reboot
> LIVVAX, it would come up as unlicensed. But then my node-specific
> startup script modifies the license back to be for LIVVAX only.
> Essentially, both nodes are "fighting" over a single record in the
> common license database.
>
> Does that sound plausible?
>
> Nathan
Each node, when booting and checking licenses, looks at the
LMF$LICENSE.LDB it "sees". For each node, the search path is
SYS$SPECIFIC:[SYSEXE],SYS$COMMON:[SYSEXE] in that order. Unless logical
LMF$LICENSE is defined, on a vanilla system the most likely place to
look for the definition is SYS$MANAGER:SYLOGICALS.COM.
You can do a DIR/FULL on the files you listed. If they have the same
file id (FID), they're the same file. If not, then some reasoning will
tell you which file SYS0 and SYS10 sees when they're booting.
Wilm Boerhout |
Zwolle, | 'These are the times that try men's souls'
The Netherlands | (Thomas Paine, The Crisis)
More information about the Info-vax
mailing list