Sponsored Content
Full Discussion: Problem With X server
Operating Systems Solaris Problem With X server Post 302221102 by incredible on Sunday 3rd of August 2008 11:42:33 AM
Old 08-03-2008
start X server with xinit command
check the processes if dtlogin daemon is started
And before that does the soft link exists?
eg ln -s /usr/X11R6/bin /usr/bin/X11

you may want to check this out
http://www.xfree86.org/

Last edited by DukeNuke2; 08-03-2008 at 01:04 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UNIX server problem

We have a site on our UNIX server which includes downloadable word and excel files. The word files are downloading files, and the excel files are trying to display in the browser instead of downloading properly. We have determined that this is not a browser issue....there is something that needs to... (1 Reply)
Discussion started by: rlwd
1 Replies

2. UNIX for Advanced & Expert Users

suse server 8.0 on hp server problem

machine: Hp Proliant DL145/Opterom 2.4GH 2*72 GBB SCSi hdd, suse: suse linux Enterprose server 8.0 for Amd 64 problem: 1. can not boot properly. have to use installation disk to boot it: enter installation and choose "boot from existing installation" and this is the only option. ( just... (1 Reply)
Discussion started by: murataht
1 Replies

3. UNIX for Advanced & Expert Users

x server problem

i can not start x server from cli mode.how to solve (1 Reply)
Discussion started by: dipanrc
1 Replies

4. HP-UX

problem after server build...

Hi, I have installed HP-UX 11.31 on a rx6600 box. The installation went fine and was completed without any errors. But wheni connect to the server using ssh, it asks for a username, when i enter it, it doesnt prompt for a password: login:username blank-------- All i could see in... (1 Reply)
Discussion started by: sag71155
1 Replies

5. Red Hat

server hang problem

Hello everybody.. I have RHEL-4 Server with kernel - Linux 2.6.9-78.0.1.ELlargesmp x86_64 It is used for Development usage.. That server got hang and so reboot was required, when checked log file i found following messages, kernel: warning: many lost ticks. kernel: Your time source... (4 Replies)
Discussion started by: laxmikant
4 Replies

6. Solaris

Server Pinging Problem

Dear all, I face some problem as below. I have a sun fire 280r server in a network. From that server i am able to ping any system in any network. But i am facing the problem when i try to ping the server from outside netwok. Once i give ping command in the server then only i try to... (1 Reply)
Discussion started by: sudhansu
1 Replies

7. Programming

Problem with Perl script after moving from a Windows/Apache Server to a UNIX server.

I have a Perl script that worked fine before moving it to justhost.com. It was on a Windows/Apache server. Just host is using UNIX. Other Perl scripts on other sites that were also moved work fine so I know Perl is functioning. The script is called cwrmail.pl and is located in my cgi-bin. When I... (9 Replies)
Discussion started by: BigBobbyB
9 Replies

8. Ubuntu

Problem in Postfix server/is my server got some attack

Hi Friends, This is logs of my mail log: mail for yahoo.com.tw is using up 4001 of 6992 active queue entries : 1 Time(s) mail for yahoo.com.tw is using up 4001 of 7018 active queue entries : 1 Time(s) mail for yahoo.com.tw is using up 4001 of 7072 active queue entries : 1 Time(s) ... (1 Reply)
Discussion started by: darakas
1 Replies

9. SCO

Server problem

We have an old server that has failed to boot and I don't know how to fix it maybe someone here could point me in the right direction. I don't know anything about this operating system The person who used to fix it has passed on so any help would be great. I am uploading some screen shots to... (6 Replies)
Discussion started by: Jafwiz
6 Replies

10. Solaris

NFS problem in server

Hi, In our production system one of the users complained of receiving the error below in the /var/adm/messages : Apr 9 00:05:03 L28emmol1 EV_AGENT: Agent Main --Estream construct failed. Err: EMULSocket::recv() Apr 9 00:05:03 L28emmol1 nfs4cbd: nfssys NFS4_SVC failed Apr 9 00:05:03... (1 Reply)
Discussion started by: anaigini45
1 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)
All times are GMT -4. The time now is 03:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy