I'm running AIX 5L v5.3 base and installed CDE is 1.0. I've seen recommendations to add "-nolisten tcp" to the args for X but anytime I try that it simply fails to start. I've tried adding it as an arg to /usr/dt/config/Xservers as well as trying to add it to the extensions variable in /usr/lpp/X11/defaults/xserverrc. Currently CDE is started via the following in the Xservers file:
Can anyone shed some light on this? I have been unable to find AIX specific guidance so far.
Hi,
Im programming a perl script which will act as a daemon listening on a tcp port (2323) and will take (<stdin>) from the client (im going to use telnet) and run the arguments from (<stdin>) against an program already on the server, which is used to list books in the library at uni.
So far... (1 Reply)
Hi..
I am using HPux11.0
i want to know if server not listening to a tcp port what should we do to resolve the problem....
in /etc/services tcp port 7108/tcp is mentioned for some perticular application..
while starting that application error is coming could not establish
listening address... (1 Reply)
I am not what I would call an experienced programmer.
I know some ksh etc..
I need to be able to listening on a port for incoming data on a ultra 10 using solaris 9. Basically all that I need to do at the moment is to log the incoming data on a specific port number.
Any ideas on how I... (6 Replies)
Hi All,
I'm running RH 9.0 on a PII box with 160MB RAM. Just downloaded RealVNC X86 Linux (version 3.3.7). How can I get the HTTP listening port up ?
Thanks,
KENT (6 Replies)
Hi
I am on solaris 8. And using xdm Xsun for X windows capabilities. Is it possible to close port 6000 and still have xdm Xsun for X windows capabilities.
I came across http://www.sunmanagers.org/pipermail/summaries/2004-May/005208.html
and neither i can close off port 6000
Rgds (2 Replies)
Hi Pals
Consider a case where the network interface is there and it is connected to a network.
Only thing left here is I need to set a static ip/ip though dhcp (though ifconfig)
I heard that it is possible to listen even if the ip address is not set. So is there any possibility of an attack over... (1 Reply)
Hello,
I was trying to find information about below rpcbind issue and how can I fix it so that, it wont happen again.
Below is the one of the vulnerability from my security team,
RPC
service name: portmapper
service protocal: udp
Portmapper found at: 327xx
service port: 327xx
... (2 Replies)
Discussion started by: system.engineer
2 Replies
LEARN ABOUT HPUX
startx
STARTX(1) General Commands Manual STARTX(1)NAME
startx - initialize an X session
SYNOPSIS
startx [ [ client ] options ... ] [ -- [ server ] [ display ] options ... ]
DESCRIPTION
The startx script is a front end to xinit(1) that provides a somewhat nicer user interface for running a single session of the X Window
System. It is often run with no arguments.
Arguments immediately following the startx command are used to start a client in the same manner as xinit(1). The special argument '--'
marks the end of client arguments and the beginning of server options. It may be convenient to specify server options with startx to
change on a per-session basis the default color depth, the server's notion of the number of dots-per-inch the display device presents, or
take advantage of a different server layout, as permitted by the Xorg(1) server and specified in the xorg.conf(5) configuration. Some
examples of specifying server arguments follow; consult the manual page for your X server to determine which arguments are legal.
startx -- -depth 16
startx -- -dpi 100
startx -- -layout Multihead
To determine the client to run, startx first looks for a file called .xinitrc in the user's home directory. If that is not found, it uses
the file xinitrc in the xinit library directory. If command line client options are given, they override this behavior and revert to the
xinit(1) behavior. To determine the server to run, startx first looks for a file called .xserverrc in the user's home directory. If that
is not found, it uses the file xserverrc in the xinit library directory. If command line server options are given, they override this
behavior and revert to the xinit(1) behavior. Users rarely need to provide a .xserverrc file. See the xinit(1) manual page for more
details on the arguments.
The system-wide xinitrc and xserverrc files are found in the /etc/X11/xinit directory.
ENVIRONMENT VARIABLES
DISPLAY This variable gets set to the name of the display to which clients should connect. Note that this gets set, not
read.
XAUTHORITY This variable, if not already defined, gets set to $(HOME)/.Xauthority. This is to prevent the X server, if not
given the -auth argument, from automatically setting up insecure host-based authentication for the local host.
See the Xserver(1) and Xsecurity(7) manual pages for more information on X client/server authentication.
FILES
$(HOME)/.xinitrc Client to run. Typically a shell script which runs many programs in the background.
$(HOME)/.xserverrc Server to run. The default is X.
/etc/X11/xinit/xinitrc Client to run if the user has no .xinitrc file.
/etc/X11/xinit/xserverrc Server to run if the user has no .xserverrc file.
SEE ALSO xinit(1), X(7), Xserver(1), Xorg(1), xorg.conf(5)X Version 11 xinit 1.3.2 STARTX(1)