10 More Discussions You Might Find Interesting
1. Solaris
I have this Xserver not display issues, I try search from the forum but found out it can have different errors from the Xerrors logs. Here I upload and hope admin can help.
root@ccs # more Xerrors
The loadable module for the display device SUNWast is not installed.
Fatal server error:... (1 Reply)
Discussion started by: mailbox80
1 Replies
2. Red Hat
Hello,
I have recently installed MySql and I encourage an error.
I am using Fedora 15 and when I am trying to start mysqld service i am getting
the following error message:
Starting mysqld (via systemctl): Job failed. See system logs and 'systemctl status' for details. If I try to start it... (4 Replies)
Discussion started by: dot_pro
4 Replies
3. UNIX for Dummies Questions & Answers
service of vsftpd is not starting .I m using centos 5 please help (2 Replies)
Discussion started by: Raj@Innodata
2 Replies
4. Solaris
I wanted to modify my Xstarup file so I can have Croatian letters but unfortunately I am unable to log in .
What I have done is
cp /dev/null /etc/dt/config/Xstartup
cat >> /etc/dt/config/Xstartup <<%EOF%
keycode 34 = bracketleft braceleft scaron Scaron
keycode 35 = bracketright... (8 Replies)
Discussion started by: solaris_user
8 Replies
5. Solaris
I have an issue here with ldap client. It stoped and won't start.
What I have got:
sadm $ tail /var/adm/messages
Apr 16 09:17:24 hostname inetd: libsldap: Status: 2 Mesg: Unable to load configuration '/var/ldap/ldap_client_file' ('').
Apr 16 09:17:24 hostname inetd: libsldap: Status: 2 ... (3 Replies)
Discussion started by: aixlover
3 Replies
6. Solaris
I have problem with my V490 server which running on solaris 8. The error show on log file
X_mkdir: nosuch file or directory
Fatal server error:
Failed to establish all listening sockets
error (pid 299): server unexpectedly died
error (pid 299): server for display :0 cant be started
... (1 Reply)
Discussion started by: shamsul
1 Replies
7. Solaris
Hi,
I need to start the Xserver process in a domain of a E25K which has installed Solaris 8, however this domain doesn't have installed a graphic card, is this possible? Or is there any way to emulate this process?
In fact I don't know how to stop or start the Xserver process, is with... (5 Replies)
Discussion started by: wolf8006
5 Replies
8. UNIX for Advanced & Expert Users
Hi,
From my workstation (win XP)I open a telnet session on Linux(Red Hat) server.
When I issue :
# xclock
I have :
Error: Can't open display:
Then :
# export DISPLAY=192.16.1.87:0.0
# xclock
Error: Can't open display: 192.16.1.87:0.0
Do you have an idea ?
Many thanks. (6 Replies)
Discussion started by: big123456
6 Replies
9. Solaris
Dear
When I restart the Xserver it works fine for less than half an hour and throw this error afterward.
After setting the display DISPLAY=10.195.2.13:0.0, I tried to run xclock. After few minutes it throws this error message
"X connection to 10.195.2.13:0.0 broken (explicit kill or... (0 Replies)
Discussion started by: tanvirscsa
0 Replies
10. HP-UX
I Need help !
We changed a WS HP 715/33 the new is a HP 715/100 ! The old one supports a HIL keyboard and mouse. The "new" one PS2 keyboard.
We changed only the hardware not the harddisk - now the Xserver didnīt start !
What have we to configure thatt the WS supports the PS2 keyboard under... (0 Replies)
Discussion started by: rbrandt1
0 Replies
XINIT(1) General Commands Manual XINIT(1)
NAME
xinit - X Window System initializer
SYNOPSIS
xinit [ [ client ] options ... ] [ -- [ server ] [ display ] options ... ]
DESCRIPTION
The xinit program is used to start the X Window System server and a first client program on systems that are not using a display manager
such as xdm(1) or in environments that use multiple window systems. When this first client exits, xinit will kill the X server and then
terminate.
If no specific client program is given on the command line, xinit will look for a file in the user's home directory called .xinitrc to run
as a shell script to start up client programs. If no such file exists, xinit will use the following as a default:
xterm -geometry +1+1 -n login -display :0
If no specific server program is given on the command line, xinit will look for a file in the user's home directory called .xserverrc to
run as a shell script to start up the server. If no such file exists, xinit will use the following as a default:
X :0
Note that this assumes that there is a program named X in the current search path. The site administrator should, therefore, make a link
to the appropriate type of server on the machine, or create a shell script that runs xinit with the appropriate server.
Note, when using a .xserverrc script be sure to ``exec'' the real X server. Failing to do this can make the X server slow to start and
exit. For example:
exec Xdisplaytype
An important point is that programs which are run by .xinitrc should be run in the background if they do not exit right away, so that they
don't prevent other programs from starting up. However, the last long-lived program started (usually a window manager or terminal emula-
tor) should be left in the foreground so that the script won't exit (which indicates that the user is done and that xinit should exit).
An alternate client and/or server may be specified on the command line. The desired client program and its arguments should be given as
the first command line arguments to xinit. To specify a particular server command line, append a double dash (--) to the xinit command
line (after any client and arguments) followed by the desired server command.
Both the client program name and the server program name must begin with a slash (/) or a period (.). Otherwise, they are treated as an
arguments to be appended to their respective startup lines. This makes it possible to add arguments (for example, foreground and back-
ground colors) without having to retype the whole command line.
If an explicit server name is not given and the first argument following the double dash (--) is a colon followed by a digit, xinit will
use that number as the display number instead of zero. All remaining arguments are appended to the server command line.
EXAMPLES
Below are several examples of how command line arguments in xinit are used.
xinit This will start up a server named X and run the user's .xinitrc, if it exists, or else start an xterm.
xinit -- /usr/local/bin/Xvnc :1
This is how one could start a specific type of server on an alternate display.
xinit -geometry =80x65+10+10 -fn 8x13 -j -fg white -bg navy
This will start up a server named X, and will append the given arguments to the default xterm command. It will ignore .xinitrc.
xinit -e widgets -- ./Xorg -l -c
This will use the command .Xorg -l -c to start the server and will append the arguments -e widgets to the default xterm command.
xinit /usr/ucb/rsh fasthost cpupig -display ws:1 -- :1 -a 2 -t 5
This will start a server named X on display 1 with the arguments -a 2 -t 5. It will then start a remote shell on the machine
fasthost in which it will run the command cpupig, telling it to display back on the local workstation.
Below is a sample .xinitrc that starts a clock, several terminals, and leaves the window manager running as the ``last'' application.
Assuming that the window manager has been configured properly, the user then chooses the ``Exit'' menu item to shut down X.
xrdb -load $HOME/.Xresources
xsetroot -solid gray &
xclock -g 50x50-0+0 -bw 0 &
xload -g 50x50-50+0 -bw 0 &
xterm -g 80x24+0+0 &
xterm -g 80x24+0-0 &
twm
Sites that want to create a common startup environment could simply create a default .xinitrc that references a site-wide startup file:
#!/bin/sh
. /usr/local/lib/site.xinitrc
Another approach is to write a script that starts xinit with a specific shell script. Such scripts are usually named x11, xstart, or
startx and are a convenient way to provide a simple interface for novice users:
#!/bin/sh
xinit /usr/local/lib/site.xinitrc -- /usr/bin/X -br
ENVIRONMENT VARIABLES
DISPLAY This variable gets set to the name of the display to which clients should connect.
XINITRC This variable specifies an init file containing shell commands to start up the initial windows. By default, .xinitrc in the
home directory will be used.
FILES
.xinitrc default client script
xterm client to run if .xinitrc does not exist
.xserverrc default server script
X server to run if .xserverrc does not exist
SEE ALSO
X(7), startx(1), Xserver(1), Xorg(1), xorg.conf(5), xterm(1)
AUTHOR
Bob Scheifler, MIT Laboratory for Computer Science
X Version 11 xinit 1.3.2 XINIT(1)