• Xmanager Enterprise Linking VM Redhat Linux AS4.7 X64–Server Configuration


    image image

    [root@localhost ~]# vi /etc/inittab

    #
    # inittab       This file describes how the INIT process should set up
    #               the system in a certain run-level.
    #
    # Author:       Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
    #               Modified for RHS Linux by Marc Ewing and Donnie Barnes
    #

    # Default runlevel. The runlevels used by RHS are:
    #   0 - halt (Do NOT set initdefault to this)
    #   1 - Single user mode
    #   2 - Multiuser, without NFS (The same as 3, if you do not have networking)
    #   3 - Full multiuser mode
    #   4 - unused
    #   5 - X11
    #   6 - reboot (Do NOT set initdefault to this)
    #
    id:5:initdefault:

    # System initialization.
    si::sysinit:/etc/rc.d/rc.sysinit

    [root@localhost ~]# vi /etc/X11/gdm/gdm.conf

    # The first form tells xdm which displays to respond to itself.
    # The second form tells xdm to forward indirect queries from hosts matching
    # the specified pattern to the indicated list of hosts.
    # The third form tells xdm to handle indirect queries using the chooser;
    # $XConsortium: Xaccess,v 1.5 91/08/26 11:52:51 rws Exp $
    #
    # Access control file for XDMCP connections
    #
    # To control Direct and Broadcast access:
    #
    #       pattern
    #
    # To control Indirect queries:
    #
    #       pattern         list of hostnames and/or macros ...
    #
    # To use the chooser:
    #
    #       pattern         CHOOSER BROADCAST
    #
    # or
    #
    #       pattern         CHOOSER list of hostnames and/or macros ...
    #
    # To define macros:
    #
    #       %name           list of hosts ...
    #
    # XDMCP is the protocol that allows remote login.  If you want to log into
    # gdm remotely (I'd never turn this on on open network, use ssh for such
    # remote usage that).  You can then run X with -query <thishost> to log in,
    # or -indirect <thishost> to run a chooser.  Look for the 'Terminal' server
    # type at the bottom of this config file.
    [xdmcp]
    # Distributions: Ship with this off.  It is never a safe thing to leave
    # out on the net.  Setting up /etc/hosts.allow and /etc/hosts.deny to only
    # allow local access is another alternative but not the safest.
    # Firewalling port 177 is the safest if you wish to have xdmcp on.
    # Read the manual for more notes on the security of XDMCP.
    Enable=true
    # Honour indirect queries, we run a chooser for these, and then redirect
    # the user to the chosen host.  Otherwise we just log the user in locally.
    #HonorIndirect=true
    # Maximum pending requests
    #MaxPending=4
    #MaxPendingIndirect=4
    # Maximum open XDMCP sessions at any point in time
    #MaxSessions=16
    # Maximum wait times
    #MaxWait=15
    #MaxWaitIndirect=15
    # How many times can a person log in from a single host.  Usually better to
    # keep low to fend off DoS attacks by running many logins from a single
    # host.  This is now set at 2 since if the server crashes then gdm doesn't
    # know for some time and wouldn't allow another session.
    #DisplaysPerHost=2
    # The number of seconds after which a non-responsive session is logged off.
    # Better keep this low.
    #PingIntervalSeconds=15
    # The port.  177 is the standard port so better keep it that way
    Port=177

    [root@localhost ~]# vi  /etc/X11/xdm/xdm-config
    ! SECURITY: do not listen for XDMCP or Chooser requests
    ! Comment out this line if you want to manage X terminals with xdm
    !DisplayManager.requestPort:    0             

    [root@localhost ~]# vi /etc/X11/xdm/Xaccess

    # The first form tells xdm which displays to respond to itself.
    # The second form tells xdm to forward indirect queries from hosts matching
    # the specified pattern to the indicated list of hosts.
    # The third form tells xdm to handle indirect queries using the chooser;
    # the chooser is directed to send its own queries out via the broadcast
    # address and display the results on the terminal.
    # The fourth form is similar to the third, except instead of using the
    # broadcast address, it sends DirectQuerys to each of the hosts in the list
    #
    # In all cases, xdm uses the first entry which matches the terminal;
    # for IndirectQuery messages only entries with right hand sides can
    # match, for Direct and Broadcast Query messages, only entries without
    # right hand sides can match.
    #

    # *                                     #any host can get a login window

    #
    # To hardwire a specific terminal to a specific host, you can
    # leave the terminal sending indirect queries to this host, and
    # use an entry of the form:
    #

    #terminal-a     host-a


    #
    # The nicest way to run the chooser is to just ask it to broadcast
    # requests to the network - that way new hosts show up automatically.
    # Sometimes, however, the chooser can't figure out how to broadcast,
    # so this may not work in all environments.
    #

    *               CHOOSER BROADCAST       #any indirect host can get a chooser

  • 相关阅读:
    paip.云计算以及分布式计算的区别
    paip.索引的种类以及实现attilax 总结
    paip.分布式应用系统java c#.net php的建设方案
    paip.提升性能--多核编程中的java .net php c++最佳实践 v2.0 cah
    paip.中文 分词 ---paoding 3.1 的使用
    paip.2013年技术趋势以及热点 v2.0 cae
    paip.为什么使用多线程的原因.
    paip.提升性能--多核cpu中的java/.net/php/c++编程
    paip.重装系统需要备份的资料总结..v2.0 cad
    paip.禁用IKAnalyzer 的默认词库.仅仅使用自定义词库.
  • 原文地址:https://www.cnblogs.com/quanweiru/p/4927598.html
Copyright © 2020-2023  润新知