Sponsored Content
Full Discussion: vncserver
Operating Systems Linux Red Hat vncserver Post 302524453 by fpmurphy on Monday 23rd of May 2011 10:50:08 AM
Old 05-23-2011
The version of vncserver you installed is not integrated with Fedora 10. it is a standalone version and has to be treated as such. Therefore commands such as
Code:
service vncserver status

will not work.

If you want a Fedora 10 enabled version, download and install the appropriate RPMs from /pub/archive/fedora/linux/releases/10. Look under "Everything/i386/os/Packages".
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

vncserver on SCo 505

I have installed vnc on my SCO 505 box. its running fin, but when I start a session and connect to it from my win machine I do get an Xsession but I only get an xterm and thats it. I know my settings are in my //.vnc/xstartup file but what exactly am I supposed to see there. will some one send... (3 Replies)
Discussion started by: franruiz
3 Replies

2. UNIX and Linux Applications

vncserver xlib error

Hello! Im running tight VNC on Red Hat Enterprise Linux 4.0. How can I increase the number of X clients that I can run in a VNC session?I need to run aproximately 500 programs in one VNC session, but at this time I can only 236 -> i've tryed to launch 250 xclock's in background and when it... (0 Replies)
Discussion started by: karpoand
0 Replies

3. Red Hat

how to use vncserver and vncviewer?

hello, I have two fedora 8 systems connected in LAN. I have typed "vncserver" on one terminal; gave a password. Then went to the next terminal and typed "vncviewer".It asked me for host server.I gave the IP address of the above system.But it prompted that "server not found". I tried "ping"... (4 Replies)
Discussion started by: nsharath
4 Replies

4. Linux

vncserver gnome display error

Hi all, I installed vncserver on fedora core 10. I am able to start vncserver and access it via vncviewer but i am not getting gnome display. I am getting the following errors. 1) The panel has encountered a fatal error: the panel could not register with bonobo activation server (error... (6 Replies)
Discussion started by: lramsb4u
6 Replies

5. Ubuntu

VNCserver not working?

Hi, I am having trouble connecting to the vncserver on my Ubuntu server 10.04.2. # vncserver :1 A VNC server is already running as :1 # ps -ef | grep vnc root 2944 1683 0 13:47 pts/0 00:00:00 grep --color=auto vnc I think I have got all the necessary binaries (below) but when I... (0 Replies)
Discussion started by: Duffs22
0 Replies

6. Red Hat

VNCSERVER Install

Hi All, Just wondering if someone can help me out here: Wanted to install vnc server on Centos 6, yum installed tigervnc but there after I do not see any services associated with it. Also, I had installed SAMBA and proceeded with SWAT installation but I am unable to access... (2 Replies)
Discussion started by: a2z1982
2 Replies

7. UNIX for Dummies Questions & Answers

Works on command line but not in script; vncserver on solaris 10

Hi guys. My first post, so be gentle... On my Solaris 10 machine vnc server is running. I need a command to extract most recent client session number (screen). So with: Code: bash-3.2# ps -ef | grep vnc | grep Xaut root 19805 19797 0 15:41:44 ? 0:01 Xvnc :4 -inetd -once... (5 Replies)
Discussion started by: cp6uja
5 Replies

8. Linux

Vncserver NOT working

Hi all, I received following messages while trying to run vncserver, what could be reason behind this. vncserver Warning: system1.pen.com:1 is taken because of /tmp/.X11-unix/X1 Remove this file if there is no X server system1.pen.com:1 Warning: system1.pen.com:2 is taken because of... (2 Replies)
Discussion started by: manalisharmabe
2 Replies

9. UNIX Desktop Questions & Answers

Unable to start vncserver

Hi, While trying to connect vncserver, i am gettting below errors: sh: /home/$USER/.vnc/$HOSTNAME:2.log: Permission denied sh: /home/$USER/.vnc/$HOSTNAME:2.pid: Permission denied New '$HOSTNAME:2 ($USER)' desktop is $HOSTNAME:2 Starting applications specified in... (1 Reply)
Discussion started by: pandeesh
1 Replies
OS-RELEASE(5)							    os-release							     OS-RELEASE(5)

NAME
os-release - Operating system identification SYNOPSIS
/etc/os-release DESCRIPTION
The /etc/os-release file contains operating system identification data. The basic file format of os-release is a newline-separated list of environment-like shell-compatible variable assignments. It is possible to source the configuration from shell scripts, however, beyond mere variable assignments no shell features are supported (this means variable expansion is explicitly not supported), allowing applications to read the file without implementing a shell compatible execution engine. Variable assignment values should be enclosed in double or single quotes if they include spaces, semicolons or other special characters outside of A-Z, a-z, 0-9. All strings should be in UTF-8 format, and non-printable characters should not be used. If double or single quotes or backslashes are to be used within variable assignments they should be escaped with backslashes, following shell style. It is not supported to concatenate multiple individually quoted strings. Lines beginning with "#" shall be ignored as comments. /etc/os-release contains data that is defined by the operating system vendor and should not be changed by the administrator. As this file only encodes names and identifiers it should not be localized. The file /etc/os-release might be a symlink to another file, but it is important that the file is available from earliest boot on, and hence must be located on the root file system. For a longer rationale for /etc/os-release please refer to the Announcement of /etc/os-release[1]. OPTIONS
The following OS identifications parameters may be set using /etc/os-release: NAME= A string identifying the operating system, without a version component, and suitable for presentation to the user. If not set defaults to NAME=Linux. Example: NAME=Fedora or NAME="Debian GNU/Linux". VERSION= A string identifying the operating system version, excluding any OS name information, possibly including a release code name, and suitable for presentation to the user. This field is optional. Example: VERSION=17 or VERSION="17 (Beefy Miracle)". ID= A lower-case string (no spaces or other characters outside of 0-9, a-z, ".", "_" and "-") identifying the operating system, excluding any version information and suitable for processing by scripts or usage in generated file names. If not set defaults to ID=linux. Example: ID=fedora or ID=debian. ID_LIKE= A space-separated list of operating system identifiers in the same syntax as the ID= setting. Should list identifiers of operating systems that are closely related to the local operating system in regards to packaging and programming interfaces, for example listing one or more OS identifiers the local OS is a derivative from. An OS should generally only list other OS identifiers it itself is a derivative from, and not any OSes that are derived from it, but symmetric relationships are possible. Build scripts and similar should check this variable if they need to identify the local operating system and the value of ID= is not recognized. Operating systems should be listed in order of how closely the local operating system relates to the listed ones, starting with the closest. This field is optional. Example: for an operating system with ID=centos an assignment of ID_LIKE="rhel fedora" would be appropriate. For an operating system with ID=ubuntu an assignment of ID_LIKE=debian is appropriate. VERSION_ID= A lower-case string (mostly numeric, no spaces or other characters outside of 0-9, a-z, ".", "_" and "-") identifying the operating system version, excluding any OS name information or release code name, and suitable for processing by scripts or usage in generated file names. This field is optional. Example: VERSION_ID=17 or VERSION_ID=11.04. PRETTY_NAME= A pretty operating system name in a format suitable for presentation to the user. May or may not contain a release code name or OS version of some kind, as suitable. If not set defaults to PRETTY_NAME="Linux". Example: PRETTY_NAME="Fedora 17 (Beefy Miracle)". ANSI_COLOR= A suggested presentation color when showing the OS name on the console. This should be specified as string suitable for inclusion in the ESC [ m ANSI/ECMA-48 escape code for setting graphical rendition. This field is optional. Example: ANSI_COLOR="0;31" for red, or ANSI_COLOR="1;34" for light blue. CPE_NAME= A CPE name for the operating system, following the Common Platform Enumeration Specification[2] as proposed by the MITRE Corporation. This field is optional. Example: CPE_NAME="cpe:/o:fedoraproject:fedora:17" HOME_URL=, SUPPORT_URL=, BUG_REPORT_URL= Links to resources on the Internet related the operating system. HOME_URL= should refer to the homepage of the of operating system, or alternatively some homepage of the specific version of the operating system. SUPPORT_URL= should refer to the main support page for the operating system, if there is any. This is primarily intended for operating systems which vendors provide support for. BUG_REPORT_URL= should refer to the main bug reporting page for the operating system, if there is any. This is primarily intended for operating systems that rely on community QA. These settings are optional, and providing only some of these settings is common. These URLs are intended to be exposed in "About this system" UIs behind links with captions such as "About this Operating System", "Obtain Support" resp. "Report a Bug". The values should be in RFC3986 format[3], and should be http: or https: URLs, and possibly mailto: or tel:. Only one URL shall be listed in each setting. If multiple resources need to be referenced it is recommended to provide an online landing page linking all available resources. Examples: HOME_URL="https://fedoraproject.org/" and BUG_REPORT_URL="https://bugzilla.redhat.com/" If you are reading this file from C code or a shell script to determine the OS or a specific version of it, use the ID and VERSION_ID fields, possibly with ID_LIKE as fallback for ID. When looking for an OS identification string for presentation to the user use the PRETTY_NAME field. Note that operating system vendors may choose not to provide version information, for example to accommodate for rolling releases. In this case VERSION and VERSION_ID may be unset. Applications should not rely on these fields to be set. Operating system vendors may extend the file format and introduce new fields. It is highly recommended to prefix new fields with an OS specific name in order to avoid name clashes. Applications reading this file must ignore unknown fields. Example: DEBIAN_BTS="debbugs://bugs.debian.org/" EXAMPLE
NAME=Fedora VERSION="17 (Beefy Miracle)" ID=fedora VERSION_ID=17 PRETTY_NAME="Fedora 17 (Beefy Miracle)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:fedoraproject:fedora:17" HOME_URL="https://fedoraproject.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" SEE ALSO
systemd(1), lsb_release(1), hostname(5), machine-id(5), machine-info(5) AUTHOR
Lennart Poettering <lennart@poettering.net> Developer NOTES
1. Announcement of /etc/os-release http://0pointer.de/blog/projects/os-release 2. Common Platform Enumeration Specification http://cpe.mitre.org/specification/ 3. RFC3986 format https://tools.ietf.org/html/rfc3986 systemd 10/07/2013 OS-RELEASE(5)
All times are GMT -4. The time now is 09:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy