• attempting data connect x.x.x.x is not same as server x.x.x.y 。由于FTP服务器要求只能将文件上传到默认文件夹下，这块没法改动， 为了测试，直接注释掉，然后集中解决storefile()的问题： 网上 说得最多的...
之前项目一直再用apache的FTPClient来进行文件的上传功能，可是最近FTP服务器地址改了，密码和账号也变了。使用FTP手动输入命令时，无账号密码可以登录成功，随意输入账号密码也能登录成功，好囧，这是什么情况？中途参与的项目，在FTP服务器发生变化后，修改服务器iP和端口地址后继续使用原来的FTPClient程序，发现无法上传文件到新地址上。
于是乎，开始各种调式和搜索，发现FTPClient的changeWorkingDirectory(path)和storeFile(filename,
input)执行后，changeWorkingDirectory函数返回的是flase失败，storeFile报异常Host
attempting data connect x.x.x.x is not same as server x.x.x.y。由于FTP服务器要求只能将文件上传到默认文件夹下，这块没法改动， 为了测试，直接注释掉，然后集中解决storefile()的问题：
网上 说得最多的是由于FTP有两种模式，一种是主动方式，另一种是被动方式，只要加上ftpClient.enterLocalPassiveMode()即可解决问题
，遂加之，发现不报异常，但是storefile执行后返回false，发现文件未上传到FTP服务器上。
网上还有一种说法是由于文件名是中文名称的原因，只要添加ftpClient.setControlEncoding("UTF-8"),并在创建目录或者storefile的时候将文件名转换编码方式即可，ftpClient.storeFile(new
String(fileName.getBytes("UTF-8"),"iso-8859-1"),fiStream);或ftpClient.makeDirectory(new String(pathName.getBytes("UTF-8"),"iso-8859-1"));即可解决问题，可我的而文件名不是中文啊！进一步排查手动FTP到服务器，使用passive命令，发现模式修改成功，但是进行put命令时会发现服务器拒绝响应，
排除不是FTP主动和被动工作方式的问题。
想到服务器的账号密码边了。在手动时输入账号和密码的时候直接回车既能连上，查看项目代码，发现无登陆模式的连接方法中有一个setRemoteVerificationEnabled(false),这个方法表示启用或禁用合适
，默认值是核实被启用。在代码中加入此函数，并显示设置enterLocalActiveMode()模式，运行后storefile返回TRUE，正常了。可是文件还是没有上传到FTP服务器， 将之前注释的changeWorkingDirectory(path)去掉注释，继续运行，终于成功上传
，可是changeWorkingDirectory(path)返回false ，好奇怪，为什么？咳，不管了问题解决了就好。  调式这个小玩意竟然花了我一天时间 ，好囧。菜鸟伤不起啊

展开全文
• 在所有节点重启kubelet试试： sudo systemctl restart kubelet.service
在所有节点重启kubelet试试：
sudo systemctl restart kubelet.service


展开全文
• Xserver - X Window System display server Synopsis X [option ...] Description X is the generic name for the X Window System display server. It is frequently a link or a copy of the appropriate ...
Table of Contents
Name
Xserver - X Window System display server
Synopsis
X [option ...]
Description
X is the generic name for the X Window System display server. It is frequently a link or a copy of the appropriate server binary for driving the most frequently used server on a given machine.
Starting the Server
The X server is usually started from the X Display Manager program xdm(1) or a similar display manager program. This utility is run from the system boot files and takes care of keeping the server running, prompting for usernames and passwords, and starting up the user sessions.
Installations that run more than one window system may need to use the xinit(1) utility instead of a display manager. However, xinit is to be considered a tool for building startup scripts and is not intended for use by end users. Site administrators are strongly urged to use a display manager, or build other interfaces for novice users.
The X server may also be started directly by the user, though this method is usually reserved for testing and is not recommended for normal operation. On some platforms, the user must have special permission to start the X server, often because access to certain devices (e.g. /dev/mouse) is restricted.
When the X server starts up, it typically takes over the display. If you are running on a workstation whose console is the display, you may not be able to log into the console while the server is running.
Options
Many X servers have device-specific command line options. See the manual pages for the individual servers for more details; a list of server-specific manual pages is provided in the SEE ALSO section below.
All of the X servers accept the command line options described below. Some X servers may have alternative ways of providing the parameters described here, but the values provided via the command line options should override values specified via other mechanisms.
:displaynumber
The X server runs as the given displaynumber, which by default is 0. If multiple X servers are to run simultaneously on a host, each must have a unique display number. See the DISPLAY NAMES section of the X(7) manual page to learn how to specify which display number clients should try to use.
-a number
sets pointer acceleration (i.e. the ratio of how much is reported to how much the user actually moved the pointer).
-ac
disables host-based access control mechanisms. Enables access by any host, and permits any host to modify the access control list. Use with extreme caution. This option exists primarily for running test suites remotely.
-audit level
sets the audit trail level. The default level is 1, meaning only connection rejections are reported. Level 2 additionally reports all successful connections and disconnects. Level 4 enables messages from the SECURITY extension, if present, including generation and revocation of authorizations and violations of the security policy. Level 0 turns off the audit trail. Audit lines are sent as standard error output.
-auth authorization-file
specifies a file which contains a collection of authorization records used to authenticate access. See also the xdm(1) and Xsecurity(7) manual pages.
bc
disables certain kinds of error checking, for bug compatibility with previous releases (e.g., to work around bugs in R2 and R3 xterms and toolkits). Deprecated.
-bs
disables backing store support on all screens.
-br
sets the default root window to solid black instead of the standard root weave pattern.
-c
turns off key-click.
c volume
sets key-click volume (allowable range: 0-100).
-cc class
sets the visual class for the root window of color screens. The class numbers are as specified in the X protocol. Not obeyed by all servers.
-co filename
sets name of RGB color database. The default is /tmp/Xorg-KEM/lib/X11/rgb.
-core
causes the server to generate a core dump on fatal errors.
-deferglyphs whichfonts
specifies the types of fonts for which the server should attempt to use deferred glyph loading. whichfonts can be all (all fonts), none (no fonts), or 16 (16 bit fonts only).
-dpi resolution
sets the resolution for all screens, in dots per inch. To be used when the server cannot determine the screen size(s) from the hardware.
dpms
enables DPMS (display power management services), where supported. The default state is platform and configuration specific.
-dpms
disables DPMS (display power management services). The default state is platform and configuration specific.
-f volume
sets feep (bell) volume (allowable range: 0-100).
-fc cursorFont
sets default cursor font.
-fn font
sets the default font.
-fp fontPath
sets the search path for fonts. This path is a comma separated list of directories which the X server searches for font databases. See the FONTS section of this manual page for more information and the default list.
-help
prints a usage message.
-I
causes all remaining command line arguments to be ignored.
-maxbigreqsize size
sets the maxmium big request to size MB.
-nolisten trans-type
disables a transport type. For example, TCP/IP connections can be disabled with -nolisten tcp. This option may be issued multiple times to disable listening to different transport types.
-noreset
prevents a server reset when the last client connection is closed. This overrides a previous -terminate command line option.
-p minutes
sets screen-saver pattern cycle time in minutes.
-pn
permits the server to continue running if it fails to establish all of its well-known sockets (connection points for clients), but establishes at least one. This option is set by default.
-nopn
causes the server to exit if it fails to establish all of its well-known sockets (connection points for clients).
-r
turns off auto-repeat.
r
turns on auto-repeat.
-s minutes
sets screen-saver timeout time in minutes.
-su
disables save under support on all screens.
-t number
sets pointer acceleration threshold in pixels (i.e. after how many pixels pointer acceleration should take effect).
-terminate
causes the server to terminate at server reset, instead of continuing to run. This overrides a previous -noreset command line option.
-to seconds
sets default connection timeout in seconds.
-tst
disables all testing extensions (e.g., XTEST, XTrap, XTestExtension1, RECORD).
ttyxx
ignored, for servers started the ancient way (from init).
v
sets video-off screen-saver preference.
-v
sets video-on screen-saver preference.
-wm
forces the default backing-store of all windows to be WhenMapped. This is a backdoor way of getting backing-store to apply to all windows. Although all mapped windows will have backing store, the backing store attribute value reported by the server for a window will be the last value established by a client. If it has never been set by a client, the server will report the default value, NotUseful. This behavior is required by the X protocol, which allows the server to exceed the client's backing store expectations but does not provide a way to tell the client that it is doing so.
-x extension
loads the specified extension at init. This is a no-op for most implementations.
[+-]xinerama
enables(+) or disables(-) the XINERAMA extension. The default state is platform and configuration specific.
Server Dependent Options
Some X servers accept the following options:
-ld kilobytes
sets the data space limit of the server to the specified number of kilobytes. A value of zero makes the data size as large as possible. The default value of -1 leaves the data space limit unchanged.
-lf files
sets the number-of-open-files limit of the server to the specified number. A value of zero makes the limit as large as possible. The default value of -1 leaves the limit unchanged.
-ls kilobytes
sets the stack space limit of the server to the specified number of kilobytes. A value of zero makes the stack size as large as possible. The default value of -1 leaves the stack space limit unchanged.
-logo
turns on the X Window System logo display in the screen-saver. There is currently no way to change this from a client.
nologo
turns off the X Window System logo display in the screen-saver. There is currently no way to change this from a client.
-render
default|mono|gray|color sets the color allocation policy that will be used by the render extension.
default
selects the default policy defined for the display depth of the X server.
mono
don't use any color cell.
gray
use a gray map of 13 color cells for the X render extension.
color
use a color cube of at most 4*4*4 colors (that is 64 color cells).
-dumbSched
disables smart scheduling on platforms that support the smart scheduler.
-schedInterval interval
sets the smart scheduler's scheduling interval to interval milliseconds.
Xdmcp Options
X servers that support XDMCP have the following options. See the X Display Manager Control Protocol specification for more information.
-query hostname
enables XDMCP and sends Query packets to the specified hostname.
enable XDMCP and broadcasts BroadcastQuery packets to the network. The first responding display manager will be chosen for the session.
Enable XDMCP and multicast BroadcastQuery packets to the network. The first responding display manager is chosen for the session. If an address is specified, the multicast is sent to that address. If no address is specified, the multicast is sent to the default XDMCP IPv6 multicast group. If a hop count is specified, it is used as the maximum hop count for the multicast. If no hop count is specified, the multicast is set to a maximum of 1 hop, to prevent the multicast from being routed beyond the local network.
-indirect hostname
enables XDMCP and send IndirectQuery packets to the specified hostname.
-port port-number
uses the specified port-number for XDMCP packets, instead of the default. This option must be specified before any -query, -broadcast, -multicast, or -indirect options.
specifies the local address to connect from (useful if the connecting host has multiple network interfaces). The local-address may be expressed in any form acceptable to the host platform's gethostbyname(3) implementation.
-once
causes the server to terminate (rather than reset) when the XDMCP session ends.
-class display-class
XDMCP has an additional display qualifier used in resource lookup for display-specific options. This option sets that value, by default it is "MIT-Unspecified" (not a very useful value).
When testing XDM-AUTHENTICATION-1, a private key is shared between the server and the manager. This option sets the value of that private data (not that it is very private, being on the command line!).
-displayID display-id
Yet another XDMCP specific value, this one allows the display manager to identify each display so that it can locate the shared key.
Xkeyboard Options
X servers that support the XKEYBOARD (a.k.a. "XKB") extension accept the following options. All layout files specified on the command line must be located in the XKB base directory or a subdirectory, and specified as the relative path from the XKB base directory. The default XKB base directory is /tmp/Xorg-KEM/lib/X11/xkb.
[+-]kb
enables(+) or disables(-) the XKEYBOARD extension.
[+-]accessx [ timeout [ timeout_mask [ feedback [ options_mask ] ] ] ]
enables(+) or disables(-) AccessX key sequences.
-xkbdir directory
base directory for keyboard layout files. This option is not available for setuid X servers (i.e., when the X server's real and effective uids are different).
-ar1 milliseconds
sets the autorepeat delay (length of time in milliseconds that a key must be depressed before autorepeat starts).
-ar2 milliseconds
sets the autorepeat interval (length of time in milliseconds that should elapse between autorepeat-generated keystrokes).
-xkbdb filename
uses filename for default keyboard keymaps.
-xkbmap filename
loads keyboard description in filename on server startup.
Security Extension Options
X servers that support the SECURITY extension accept the following option:
-sp filename
causes the server to attempt to read and interpret filename as a security policy file with the format described below. The file is read at server startup and reread at each server reset.
The syntax of the security policy file is as follows. Notation: "*" means zero or more occurrences of the preceding element, and "+" means one or more occurrences. To interpret , ignore the text after the /; it is used to distinguish between instances of  in the next section.

::=  *
::=  '/n'
::=  |  |  |
::= # * '/n'
::=  '/n'
::= sitepolicy  '/n'
::= property    '/n'
::=
::= any | root |
::=  |
::=  =
::= [  |  |  ]*
::= r | w | d
::= a | i | e
::=  |  |
::=  " * "
::=  ' * '
::=  +
::= [ ' ' | '/t' ]*
Character sets:
::= any character except '/n'
::= any character except "
::= any character except '
::= any character except those in
The semantics associated with the above syntax are as follows.
, the first line in the file, specifies the file format version. If the server does not recognize the version , it ignores the rest of the file. The version string for the file format described here is "version-1" .
Once past the , lines that do not match the above syntax are ignored.
lines are ignored.
lines are currently ignored. They are intended to specify the site policies used by the XC-QUERY-SECURITY-1 authorization method.
lines specify how the server should react to untrusted client requests that affect the X Window property named . The rest of this section describes the interpretation of an .
For an  to apply to a given instance of ,  must be on a window that is in the set of windows specified by . If  is any, the rule applies to  on any window. If  is root, the rule applies to  only on root windows.
If  is , the following apply. If  is a , the rule applies when the window also has that , regardless of its value. If  is a ,  must also have the value specified by . In this case, the property must have type STRING and format 8, and should contain one or more null-terminated strings. If any of the strings match , the rule applies.
The definition of string matching is simple case-sensitive string comparison with one elaboration: the occurrence of the character '*' in  is a wildcard meaning "any string." A  can contain multiple wildcards anywhere in the string. For example, "x*" matches strings that begin with x, "*x" matches strings that end with x, "*x*" matches strings containing x, and "x*y*" matches strings that start with x and subsequently contain y.
There may be multiple  lines for a given . The rules are tested in the order that they appear in the file. The first rule that applies is used.
specify operations that untrusted clients may attempt, and the actions that the server should take in response to those operations.
can be r (read), w (write), or d (delete). The following table shows how X Protocol property requests map to these operations in The Open Group server implementation.

GetProperty    r, or r and d if delete = True
ChangeProperty    w
RotateProperties    r and w
DeleteProperty    d
ListProperties    none, untrusted clients can always list all properties
can be a (allow), i (ignore), or e (error). Allow means execute the request as if it had been issued by a trusted client. Ignore means treat the request as a no-op. In the case of GetProperty, ignore means return an empty property value if the property exists, regardless of its actual value. Error means do not execute the request and return a BadAtom error with the atom set to the property name. Error is the default action for all properties, including those not listed in the security policy file.
An  applies to all s that follow it, until the next  is encountered. Thus, irwad means ignore read and write, allow delete.
GetProperty and RotateProperties may do multiple operations (r and d, or r and w). If different actions apply to the operations, the most severe action is applied to the whole request; there is no partial request execution. The severity ordering is: allow < ignore < error. Thus, if the  for a property are ired (ignore read, error delete), and an untrusted client attempts GetProperty on that property with delete = True, an error is returned, but the property value is not. Similarly, if any of the properties in a RotateProperties do not allow both read and write, an error is returned without changing any property values.
Here is an example security policy file.

version-1
# Allow reading of application resources, but not writing.
property RESOURCE_MANAGER    root    ar iw
property SCREEN_RESOURCES    root    ar iw
# Ignore attempts to use cut buffers.  Giving errors causes apps to crash,
# and allowing access may give away too much information.
property CUT_BUFFER0    root    irw
property CUT_BUFFER1    root    irw
property CUT_BUFFER2    root    irw
property CUT_BUFFER3    root    irw
property CUT_BUFFER4    root    irw
property CUT_BUFFER5    root    irw
property CUT_BUFFER6    root    irw
property CUT_BUFFER7    root    irw
# If you are using Motif, you probably want these.
property _MOTIF_DEFAULT_BINDINGS    root    ar iw
property _MOTIF_DRAG_WINDOW    root    ar iw
property _MOTIF_DRAG_TARGETS    any     ar iw
property _MOTIF_DRAG_ATOMS    any     ar iw
property _MOTIF_DRAG_ATOM_PAIRS    any     ar iw
# The next two rules let xwininfo -tree work when untrusted.
property WM_NAME    any    ar
# Allow read of WM_CLASS, but only for windows with WM_NAME.
# This might be more restrictive than necessary, but demonstrates
# the  facility, and is also an attempt to
# say "top level windows only."
property WM_CLASS    WM_NAME    ar
# These next three let xlsclients work untrusted.  Think carefully
# before including these; giving away the client machine name and command
# may be exposing too much.
property WM_STATE    WM_NAME    ar
property WM_CLIENT_MACHINE    WM_NAME    ar
property WM_COMMAND    WM_NAME    ar
# To let untrusted clients use the standard colormaps created by
# xstdcmap, include these lines.
property RGB_DEFAULT_MAP    root    ar
property RGB_BEST_MAP    root    ar
property RGB_RED_MAP    root    ar
property RGB_GREEN_MAP    root    ar
property RGB_BLUE_MAP    root    ar
property RGB_GRAY_MAP    root    ar
# To let untrusted clients use the color management database created
# by xcmsdb, include these lines.
property XDCCC_LINEAR_RGB_CORRECTION    root    ar
property XDCCC_LINEAR_RGB_MATRICES    root    ar
property XDCCC_GRAY_SCREENWHITEPOINT    root    ar
property XDCCC_GRAY_CORRECTION    root    ar
# To let untrusted clients use the overlay visuals that many vendors
# support, include this line.
property SERVER_OVERLAY_VISUALS    root    ar
# Dumb examples to show other capabilities.
# oddball property names and explicit specification of error conditions
property "property with spaces"    'property with "'    aw er ed
# Allow deletion of Woo-Hoo if window also has property OhBoy with value
# ending in "son".  Reads and writes will cause an error.
property Woo-Hoo    OhBoy = "*son"    ad
Network Connections
The X server supports client connections via a platform-dependent subset of the following transport types: TCP/IP, Unix Domain sockets, DECnet, and several varieties of SVR4 local connections. See the DISPLAY NAMES section of the X(7) manual page to learn how to specify which transport type clients should try to use.
Granting Access
The X server implements a platform-dependent subset of the following authorization protocols: MIT-MAGIC-COOKIE-1, XDM-AUTHORIZATION-1, XDM-AUTHORIZATION-2, SUN-DES-1, and MIT-KERBEROS-5. See the Xsecurity(7) manual page for information on the operation of these protocols.
Authorization data required by the above protocols is passed to the server in a private file named with the -auth command line option. Each time the server is about to accept the first connection after a reset (or when the server is starting), it reads this file. If this file contains any authorization records, the local host is not automatically allowed access to the server, and only clients which send one of the authorization records contained in the file in the connection setup information will be allowed access. See the Xau manual page for a description of the binary format of this file. See xauth(1) for maintenance of this file, and distribution of its contents to remote hosts.
The X server also uses a host-based access control list for deciding whether or not to accept connections from clients on a particular machine. If no other authorization mechanism is being used, this list initially consists of the host on which the server is running as well as any machines listed in the file /etc/Xn.hosts, where n is the display number of the server. Each line of the file should contain either an Internet hostname (e.g. expo.lcs.mit.edu) or a DECnet hostname in double colon format (e.g. hydra::) or a complete name in the format family:name as described in the xhost(1) manual page. There should be no leading or trailing spaces on any lines. For example:

joesworkstation
corporate.company.com
star::
inet:bigcpu
local:
Users can add or remove hosts from this list and enable or disable access control using the xhost command from the same machine as the server.
If the X FireWall Proxy (xfwp) is being used without a sitepolicy, host-based authorization must be turned on for clients to be able to connect to the X server via the xfwp. If xfwp is run without a configuration file and thus no sitepolicy is defined, if xfwp is using an X server where xhost + has been run to turn off host-based authorization checks, when a client tries to connect to this X server via xfwp, the X server will deny the connection. See xfwp(1) for more information about this proxy.
The X protocol intrinsically does not have any notion of window operation permissions or place any restrictions on what a client can do; if a program can connect to a display, it has full run of the screen. X servers that support the SECURITY extension fare better because clients can be designated untrusted via the authorization they use to connect; see the xauth(1) manual page for details. Restrictions are imposed on untrusted clients that curtail the mischief they can do. See the SECURITY extension specification for a complete list of these restrictions.
Sites that have better authentication and authorization systems might wish to make use of the hooks in the libraries and the server to provide additional security models.
Signals
The X server attaches special meaning to the following signals:
SIGHUP
This signal causes the server to close all existing connections, free all resources, and restore all defaults. It is sent by the display manager whenever the main user's main application (usually an xterm or window manager) exits to force the server to clean up and prepare for the next user.
SIGTERM
This signal causes the server to exit cleanly.
SIGUSR1
This signal is used quite differently from either of the above. When the server starts, it checks to see if it has inherited SIGUSR1 as SIG_IGN instead of the usual SIG_DFL. In this case, the server sends a SIGUSR1 to its parent process after it has set up the various connection schemes. Xdm uses this feature to recognize when connecting to the server is possible.
Fonts
The X server can obtain fonts from directories and/or from font servers. The list of directories and font servers the X server uses when trying to open a font is controlled by the font path.
The default font path is /tmp/Xorg-KEM/lib/X11/fonts/misc/, /tmp/Xorg-KEM/lib/X11/fonts/TTF/, /tmp/Xorg-KEM/lib/X11/fonts/Type1/, /tmp/Xorg-KEM/lib/X11/fonts/CID/, /tmp/Xorg-KEM/lib/X11/fonts/75dpi/, /tmp/Xorg-KEM/lib/X11/fonts/100dpi/ .
The font path can be set with the -fp option or by xset(1) after the server has started.
Files
/etc/Xn.hosts
Initial access control list for display number n
/tmp/Xorg-KEM/lib/X11/fonts/misc,/tmp/Xorg-KEM/lib/X11/fonts/75dpi,/tmp/Xorg-KEM/lib/X11/fonts/100dpi
Bitmap font directories
/tmp/Xorg-KEM/lib/X11/fonts/TTF,/tmp/Xorg-KEM/lib/X11/fonts/Speedo,/tmp/Xorg-KEM/lib/X11/fonts/Type1
Outline font directories
/tmp/Xorg-KEM/lib/X11/rgb.txt
Color database
/tmp/.X11-unix/Xn
Unix domain socket for display number n
/tmp/rcXn
Kerberos 5 replay cache for display number n
Error log file for display number n if run from init(8)
/tmp/Xorg-KEM/lib/X11/xdm/xdm-errors
Default error log file if the server is run from xdm(1)
General information: X(7)
Protocols: X Window System Protocol, The X Font Service Protocol, X Display Manager Control Protocol
Fonts: bdftopcf(1) , mkfontdir(1) , mkfontscale(1) , xfs(1) , xlsfonts(1) , xfontsel(1) , xfd(1) , X Logical Font Description Conventions
Security: Xsecurity(7) , xauth(1) , Xau(1) , xdm(1) , xhost(1) , xfwp(1) , Security Extension Specification
Starting the server: xdm(1) , xinit(1)
Controlling the server once started: xset(1) , xsetroot(1) , xhost(1)
Server-specific man pages: Xdec(1) , XmacII(1) , Xsun(1) , Xnest(1) , Xvfb(1) , XFree86(1) , XDarwin(1) .
Server internal documentation: Definition of the Porting Layer for the X v11 Sample Server
Authors
The sample server was originally written by Susan Angebranndt, Raymond Drewry, Philip Karlton, and Todd Newman, from Digital Equipment Corporation, with support from a large cast. It has since been extensively rewritten by Keith Packard and Bob Scheifler, from MIT. Dave Wiggins took over post-R5 and made substantial improvements.
* Name
* Synopsis
* Description
* Starting the Server
* Options
* Server Dependent Options
* Xdmcp Options
* Xkeyboard Options
* Security Extension Options
* Network Connections
* Granting Access
* Signals
* Fonts
* Files
* Authors
展开全文
• xwindows体系中，提供界面显示，响应外设操作的是xserver，而运行程序业务逻辑，接受xserver发来的各种事件通知的，是xclient。当xclient和xserver 在同一台机器上的时候，这种情况下，应用程序调用xclient的接口...
在xwindows体系中，提供界面显示，响应外设操作的是xserver，而运行程序业务逻辑，接受xserver发来的各种事件通知的，是xclient。当xclient和xserver 在同一台机器上的时候，这种情况下，应用程序调用xclient的接口请求xserver为创建窗口，应用程序可以通过xlib库的过程调用请求xserver创建窗口中子元素，例如滑动条，按钮等。而xserver的作用是提供在屏幕上绘制基础元素的功能，例如填色，画线，画圆等动作，xserver会通过调用底层驱动程序完成这些功能。而xclient通过x协议向xserver发送请求去完成对应的界面操作。下面是网上一个说的比较清楚的例子：如果从一台 XP上用Reflection通过 XDMCP 登录到一台 Linux服务器，我们很容易将Reflection当成客户端，而将Linux机器当成服务器。这就完全搞错了。理解了Xwindow的工作原理，这个区别就会很明显。X server 不是指某台机器，而是指一个进程，它负责接受客户的要求，在屏幕上显示客户请求的图形，并且把消息(键盘，鼠标，窗口消息)通知客户程序。比如上面说的Reflection，它其实是才是Xserver，它负责控制那台XP上的显示，Linux机器上的程序，xterm, xxgdb, dtwm(CDE的窗口管理器)，……是客户程序。它们通常会使用TCP 6000 号端口连接XP，而XP的6000号端口是由Reflection绑定并侦听的，显然这里Reflection才是Xserver。比如，当你通过telnet 启动Linux机器上的xterm，就会在Reflection 的屏幕上显示一个窗口。实际发生的事情是：xterm 请求连接XP的6000 号端口和Reflection，跟Reflection建立连接，然后xterm请求得到资源，然后xterm 请求在屏幕上显示一个窗口。当在xterm 的窗口里按下”A”键时，Reflection 会把这个事件通知 xterm 进程，然后xterm 会发送数据报，请求Reflection, “请在坐标(100,30)处显示一个字母A，然后在后面显示一个矩形作为光标。” 这样xterm 窗口里就会多显示一个字母。至于KDE和Gnome，他们是桌面系统不是Xwindow，他们只是一些运行在Xwindow上的程序，他们发出要显示什么东西的请求，比如要在桌面底部显示一个面板、在桌面显示些图标。http://blog.sina.com.cn/s/blog_4e415c0b0100lulu.html
展开全文
• 1、安装服务器 SQLEXPR_x64_CHS.exe 双击运行 选择安装 全新安装或向现有安装添加功能 学习用使用默认实例即可。 这个账号密码是用于管理sqlserver的服务，直接使用server2008的管理员用户以及对应的...
• 1. AbstractThis report analyzes the infra-structure of porting layer in X Server side, and gives a guide of how to port X Server in Maemo to a target p
• 您需要安装OS X 10.10或OS X 10.11以及OS X server v4 或 OS X server v5”， 我自己本身的MAC 中的一个server.app是和我当前的系统是不兼容的， 此时我们需要自己下载一个OS X server重新安装， 在Mac AppSt
• ## xserver源码分析

千次阅读 2017-12-11 18:45:45
xserver源码分析之解析xorg.conf（main函数过程） http://blog.csdn.net/w6980112/article/details/49615859 xserver资源介绍 http://www.newsmth.net/nForum/#!article/THOSS/9143 xorg-xserv
• 主要特点：1，Server/Client网络模型。2，通过扩展使它保持”与时俱进”。 Linux内核是没有GUI图形显示的，X Window的目标就是提供GUI的显示。 为啥要命名为X呢，因为英文字母X就在W(indow)后面，戏称为下一版的新...
• ## xserver相关知识汇总

千次阅读 2017-11-07 11:13:55
本文主要是从以下几个方面介绍xorg-xserver 相关的知识  1.linux系统图形界面框架 2.xserverx client启动过程 3.图形2d，3d加速原理简介 4.xserver主分支代码解析。 5.xserver,xclient协议简介 6.一个基于...
• ## CentOS 安装xserver

千次阅读 2014-10-21 20:41:39
1‘安装xserver； 2’安装
• X Server是一个广泛使用的图形引擎，提供用户界面绘画的基础图形原语以及用户事件的截获和发布功能。Xserver的图形操作可以由软件实现，然而，很多的显卡提供了硬件加速功能。如果利用这些硬件加速功能来实现Xserver...
• http://sourceforge.net/projects/xming/?source=pdlp X
• ## Linux 退出xserver

万次阅读 2014-12-29 20:56:41
如果想切换至纯粹一点的命令字符console下，一般人会认为切换Ctrl+Alt+F1(或者F2-F6都可以)。默认下，Ctrl+Alt+F7是图形界面（当然，各个Linux发行版本会有所差异）。... 3（前提有root权限），即可关闭X Server
• ## VcXsrv Windows XServer

千次阅读 2013-06-26 11:31:15
发现一个windows下开源且好用X Server. http://sourceforge.net/projects/vcxsrv/ Windows X-server based on the xorg git sources (like xming or cygwin's xwin), but compiled with Visual C++ 2010. Source ...
• ## Xserver 目录布局

千次阅读 2011-10-26 10:53:57
Xserver 目录布局  目录名 解释 dix/ X的设备独立部分，例如：这些代码用于发送请求(看Dispatch() 在 dix/dispatch.c中)以及处理资源。Main()函数就存于main.c中。 doc/ ...
• : cannot connect to X server The X Window System (X11, or simply X) is a windowing system for bitmap displays, common on Unix-like operating systems. X 窗口系统 (X Window System，X11 或 X) 是一种以...
• Failed to Start the X server
• 解决Navicate连接MySQL数据库报错： 2003 - Can't connect to MySQL server on 'x.x.x.x' (10038) 1130 - Host 'x.x.x.x' is not allowed to connect to this MySQL server
• 本文主要是从以下几个方面介绍xorg-xserver 相关的知识 1.linux系统图形界面框架 2.xserverx client启动过程 3.图形2d，3d加速原理简介 4.xserver主分支代码解析。 5.xserver,xclient协议简介 6.一个基于...
• 因为他有相当优良的 X Server/X Client 设计系统。 什么是 X ServerX Client 呢？X 在设计的时候， 就希望可以达到多人联机进入主机利用图形界面的功能，于是他便发展出这样的一个主从架构。 这个主从架构可以让...
• 在Windows 2008 运行excel 文件需要在服务器上配置的环境：1、服务管理器-> 功能-> 添加功能-> 桌面体验->默认安装・Windows 2008 Server x64Please make this folder.C:/Windows/SysWOW64/config/systemprofile/...
• ## xserver框架浅析

千次阅读 2010-04-03 10:37:00
其实说白了，在linux系统上面，驱动是分好几部分的，如果我们从最上层来看，我们看到的是图形界面，也就是xserver，实际上xserver这里有这里的驱动层。以input为例吧，我们看看这个地方。http://x
• I want to use wb_view on remote server and view it from local client. However, when I use ssh user@localhost to login to the server, it reports errors as ...wb_view: cannot connect to X server...
• ## 启动一个XServer

千次阅读 2015-01-09 22:33:01
你想要在你的Linux服务器上启动一个X server，这样你就可以运行基于图形用户界面的软件应用程序了。   解决方案： （1）手动启动，运行X命令 （2）运行init 5或telinit 5 （3）修改/etc/inittab，并重启服务器...
• 本例介绍以U盘方式，通过ServerGuide引导在System x 服务器上安装Windows Server 2012 R2操作系统。   本文是《System x 服务器使用ServerGuide引导光盘安装Windows Server 2008 R2操作系统》（知识库编号：...
• windows server 2019 安装EMQX，在命令行运行时，总是提示escript.exe错误，经过一番折腾，发再在安装了 Erlang 语言包后，就可以正常运行了。
• ## 如何升级Xserver

千次阅读 2009-11-26 17:17:00
今天就花了点时间把我的Xserver升级了一下。顺便把这些问题记录一下，以备往后参考。 目标环境：Intel Q35 platformFedora 10 升级步骤：1. 下载必须的库。 xorg-server-1.6.5.tar.bz2 依赖库

...