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

Conference noted::seal

Title:SEAL
Moderator:GALVIA::SMITH
Created:Mon Mar 21 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1989
Total number of notes:8209

1747.0. "/var/X11/xdm/xdm-errors messages" by GIDDAY::CAMERON (And there shall come FORTH (Isaiah 11:1)) Wed Jan 29 1997 23:10

    Digital UNIX V3.2d-1
    Altavista Firewall for Digital Unix V2.1
    
    I won't IPMT this just yet, I'd like to ask if anybody has come across
    it first.  It's not a severe problem.
    
    Customer reports that every second a line is added to
    /var/X11/xdm/xdm-errors provided the console is not logged in.  The
    line is the typical rejection due to X server security:
    
        "AUDIT: Tue Jan ..... 95 X: client 4 rejected from IP 127.0.0.1
    port 9999"
    
    What is causing this?  It implies a client is constantly trying to
    connect to the X server from the local host.
    
    James Cameron
T.RTitleUserPersonal
Name
DateLines
1747.1alarmd causing the errorCSC32::SHEAFFERWed Mar 12 1997 19:3521
    Hi James
    
    I had a customer who had the same problem call in today.  The errors
    occur because alarmd is running and always attempting to update the
    background of the display to reflect the current state of the firewall.
    The display cannot be updated since an X session is not active which 
    results in the errors in xdm-errors.
    
    The workaround is to either leave an X session running on the console or
    edit the xdm configuration file so that errors are sent to /dev/null.
    In /var/X11/xdm/xdm-config change the following and restart xdm.
    
    DisplayManager.errorLogFile:    /usr/var/X11/xdm/xdm-errors
    
    to
    
    DisplayManager.errorLogFile:    /dev/null
    
    Danny Sheaffer
    [email protected]
    
1747.2You can switch off the background colour control!GALVIA::SMITHThu Mar 13 1997 05:509
    You can disable alarmd's screen background update by setting the
    relevant variable in /usr/dfws/config/firewall.conf to FALSE. Check
    firewall.conf for the relevant config var.
    
    However the problem described in .0 is most likely to be related to a
    customisation of the X display mechanism and/or the auditing system
    on the firewall. I wonder why the customer made these changes.
    
    Mark