[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9134.0. "Xjoin not updating expired client list!" by CSC32::A_LICAUSE () Wed Mar 12 1997 08:34

    I have a customer that is running xjoin on his V4.0A DUNIX system and
    they are experiencing several problems.
    
    1) When they update their data bases, it seems that xjoin is placing
       a series of ^C's in bootptab.  As a result the xjoin interface is
       then interpreting these control characters as bogus group names
       and reports "duplicate group name".
    
    2) The xjoin display does not appear to be updating the expired client
       list.  What should be happening here?  Does xjoin receive realtime
       updates or does something need to be done in the configuration to
       force database updates.
    
    3) Customer has heard that there is a new version of xjoin available
       and would like to know when it will show up on the DUNIX platform?
    
    
    Please excuse any mis or missing information.  I'm new to this
    interface and don't have a good base on which to test.
    
    thanks,
    Al
T.RTitleUserPersonal
Name
DateLines
9134.1can't run both at onceSMURF::DUSTINThu Mar 13 1997 09:3911
    You can't run xjoin while the dhcp daemon (joind) is running,
    since there's a database that each of these programs needs to access
    and potentially update.  So if you are running xjoin and expecting
    things to happen while the daemon is running, and expecting to see
    updates in real-time, forget it.
    
    When xjoin starts up, it displays a warning if the daemon is running
    and you have to press "OK" in order to continue..
    
    John
    
9134.2Thanks, but what should we see?CSC32::A_LICAUSEThu Mar 13 1997 11:0411
    Ok thanks.  
    
    I found that the customer had joind running continuously instead of
    starting on demand from inetd.  On my system, joind does run on demand, 
    but I'm still seeing very old expired leases.
    
    Shouldn't this old information be purged from the database after they
    expire?
    
    Al