Sponsored Content
Special Forums UNIX Desktop Questions & Answers Where is xwindow start script Post 302272893 by glen.barber on Thursday 1st of January 2009 05:37:02 PM
Old 01-01-2009
Depends on the desktop environment, if you don't have an existing $HOME/.xinitrc file.

If using KDE, look in $HOME/.kde/Autostart .
Not sure about GNOME.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO os5 xwindow

I acciedentaly terminated the x window session on my sco os5 machine. Can somone help me get it going again with out rebooting? Another ? Does anyone know where I can get the VNC version for SCO or can some one help me make changes to the RH version to work for SCO OS5. Thanks. (2 Replies)
Discussion started by: ruizf
2 Replies

2. UNIX for Dummies Questions & Answers

xwindow on old computer

hello at first sorry for my english... i know it isn't good but i hope you can understand me i want to install xwindow on my old pentium133MHz, 49MB ram memory, graphic card - stb horizon64 1MB (with old monochromatic monitor - horizontal 30.6-36.0, vertical 50-90) all this under redhat6.1...... (1 Reply)
Discussion started by: pgas
1 Replies

3. UNIX for Dummies Questions & Answers

XWindow problems

ok, i've got a FreeBSD box, and it doesn't like my monitor. At all. The first time i installed BSD, it wouldn't write the changes. I reformated and reinstalled, and this time it would write, but when i went to load the x server with startx it would go through the load process, but say "no screens"... (4 Replies)
Discussion started by: GirlsHackBetter
4 Replies

4. UNIX for Dummies Questions & Answers

Xwindow display

I am installing Oracle 10g on UNIX. I have prepared the server in various fields. Then when I started installation, one error message came out like this: Could not execute auto check for display colors using command /usr/openwin/bin/xdpyinfo. Check if the DISPLAY variable is set. So I check... (3 Replies)
Discussion started by: duke0001
3 Replies

5. Shell Programming and Scripting

command to exit xwindow

What is the command to exit xwindow when i am in xwindow's terminal. Thanks in advance. (3 Replies)
Discussion started by: uativan
3 Replies

6. UNIX for Dummies Questions & Answers

Help with Xwindow on Linux

Hi, On my PC which is a XP, I have installed SSH client from www.ssh.com company. Linux server is a CentOS version 5. Before using my application, I want to test it and I am trying to get the xclock display back to my window and it's not working. Any idea. #... (4 Replies)
Discussion started by: samnyc
4 Replies

7. Red Hat

XWindow is not enabling !!!

Dear Experts, Our system admin is struggling over a month with an issue regarding xwindow. RHEL 5.4 is our server OS. whenever I export Display with my machine IP and run xclock. It is not working. We are using DHCP. Please tell me what checks and actions should be taken from our sys admin point... (8 Replies)
Discussion started by: saifurshaon
8 Replies

8. UNIX for Dummies Questions & Answers

XWindow Tool

Hi Guys can any one help me in this regard .. I'm using Reflaction and xManager but I want list of another xWindow tools between Unix and Windows .. Pls advice .. (1 Reply)
Discussion started by: top.level
1 Replies

9. UNIX for Dummies Questions & Answers

Questions on CLI and xwindow

Hi, I was not sure about the terminology of the thing that I am about to explain, so it was very difficult to find relevant search results. I want to use my computer using the ctrl+alt+f1 CLI without using a graphical system. However, at the same time, I would also like to do basic tasks like... (6 Replies)
Discussion started by: jamie_123
6 Replies

10. Red Hat

Installing xwindow on RHEL (offline)

I need to install xwindow on my RHEL 7.2 server which is behind a firewall and no access to internet. If I run the below code, it will not able to install, as my server dont have internet connection. yum -y install xterm* xorg* xclock xauth Do you know, where can I get the required binaries... (2 Replies)
Discussion started by: karumudi7
2 Replies
vncserver(1)						     Virtual Network Computing						      vncserver(1)

NAME
vncserver - start or stop a VNC server SYNOPSIS
vncserver [:display#] [-name desktop-name] [-geometry widthxheight] [-depth depth] [-pixelformat format] [-fp font-path] [-fg] [-autokill] [Xvnc-options...] vncserver -kill :display# DESCRIPTION
vncserver is used to start a VNC (Virtual Network Computing) desktop. vncserver is a Perl script which simplifies the process of starting an Xvnc server. It runs Xvnc with appropriate options and starts a window manager on the VNC desktop. vncserver can be run with no options at all. In this case it will choose the first available display number (usually :1), start Xvnc with that display number, and start the default window manager in the Xvnc session. You can also specify the display number, in which case vnc- server will attempt to start Xvnc with that display number and exit if the display number is not available. For example: vncserver :13 Editing the file $HOME/.vnc/xstartup allows you to change the applications run at startup (but note that this will not affect an existing VNC session.) OPTIONS
You can get a list of options by passing -h as an option to vncserver. In addition to the options listed below, any unrecognised options will be passed to Xvnc - see the Xvnc man page, or "Xvnc -help", for details. -name desktop-name Each VNC desktop has a name which may be displayed by the viewer. The desktop name defaults to "host:display# (username)", but you can change it with this option. The desktop name option is passed to the xstartup script via the $VNCDESKTOP environment variable, which allows you to run a different set of applications depending on the name of the desktop. -geometry widthxheight Specify the size of the VNC desktop to be created. Default is 1024x768. -depth depth Specify the pixel depth (in bits) of the VNC desktop to be created. Default is 24. Other possible values are 8, 15 and 16 - any- thing else is likely to cause strange behaviour by applications. -pixelformat format Specify pixel format for Xvnc to use (BGRnnn or RGBnnn). The default for depth 8 is BGR233 (meaning the most significant two bits represent blue, the next three green, and the least significant three represent red), the default for depth 16 is RGB565, and the default for depth 24 is RGB888. -cc 3 As an alternative to the default TrueColor visual, this allows you to run an Xvnc server with a PseudoColor visual (i.e. one which uses a color map or palette), which can be useful for running some old X applications which only work on such a display. Values other than 3 (PseudoColor) and 4 (TrueColor) for the -cc option may result in strange behaviour, and PseudoColor desktops must have an 8-bit depth. -kill :display# This kills a VNC desktop previously started with vncserver. It does this by killing the Xvnc process, whose process ID is stored in the file "$HOME/.vnc/host:display#.pid". The -kill option ignores anything preceding the first colon (":") in the display argument. Thus, you can invoke "vncserver -kill $DISPLAY", for example at the end of your xstartup file after a particular application exits. -list Lists running VNC servers. -fp font-path If the vncserver script detects that the X Font Server (XFS) is running, it will attempt to start Xvnc and configure Xvnc to use XFS for font handling. Otherwise, if XFS is not running, the vncserver script will attempt to start Xvnc and allow Xvnc to use its own preferred method of font handling (which may be a hard-coded font path or, on more recent systems, a font catalog.) In any case, if Xvnc fails to start, the vncserver script will then attempt to determine an appropriate X font path for this system and start Xvnc using that font path. The -fp argument allows you to override the above fallback logic and specify a font path for Xvnc to use. -fg Runs Xvnc as a foreground process. This has two effects: (1) The VNC server can be aborted with CTRL-C, and (2) the VNC server will exit as soon as the user logs out of the window manager in the VNC session. This may be necessary when launching TigerVNC from within certain grid computing environments. -autokill Automatically kill Xvnc whenever the xstartup script exits. In most cases, this has the effect of terminating Xvnc when the user logs out of the window manager. FILES
Several VNC-related files are found in the directory $HOME/.vnc: $HOME/.vnc/xstartup A shell script specifying X applications to be run when a VNC desktop is started. If this file does not exist, then vncserver will create a default xstartup script which attempts to launch your chosen window manager. $HOME/.vnc/passwd The VNC password file. $HOME/.vnc/host:display#.log The log file for Xvnc and applications started in xstartup. $HOME/.vnc/host:display#.pid Identifies the Xvnc process ID, used by the -kill option. SEE ALSO
vncviewer(1), vncpasswd(1), vncconfig(1), Xvnc(1) http://www.tigervnc.org AUTHOR
Tristan Richardson, RealVNC Ltd. D. R. Commander VNC was originally developed by the RealVNC team while at Olivetti Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people participated in development, testing and support. TigerVNC 13 Mar 2011 vncserver(1)
All times are GMT -4. The time now is 06:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy