03-08-2013
No , he cannot .
I killed the noaccess session but once I connected again ,
the noaccess session process started again.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Anyone know of a site where I can download a copy (non-evaluation copy and preferably free. ;) nods to Neo's post in UNIX Operating System thread) of VNC for RedHat 8? Thanks in advance. (7 Replies)
Discussion started by: google
7 Replies
2. Solaris
my desktop is a linux box, and I was wondering if there was a way to leverage X11/associated applications on a v440 remotely...
like "Sun Update Connection"...thanks,
manny (4 Replies)
Discussion started by: mr_manny
4 Replies
3. UNIX and Linux Applications
Greetings all,
I'm on a solaris 9 system with vnc-4.1.2 installed. I had a connection to a vnc server that suddenly started sapping up cpu cycles - getting up around 13%. I killed the server instance, and now when I try to start a new server, i get the following message:
"vncserver: socket... (0 Replies)
Discussion started by: mike_q
0 Replies
4. Linux
Hi,
This has been extremely frustrating, and I need help figuring this one out!
I am running Fedora 7 on computer A, and am VNCing into it from my Mac using Chicken of the VNC. For Sarah, everything works fine. However for Bob, the toolbar along the top is missing and every... (0 Replies)
Discussion started by: user23
0 Replies
5. Solaris
Our current VNC setup is for only 1 user login, but this login can not access a few of the programs that I need. How can I add additional logins to VNC? I have only been able to find the logs in .vnc and the usr/bin scripts. (1 Reply)
Discussion started by: gcad76
1 Replies
6. Solaris
M running solaris 10 u8 my vncserver is running on :0 .. and when i try to connect it through tight vncview i can see just see the screen .. with no terminal .. what could be the issue for it ? and what i need to check for it ? (2 Replies)
Discussion started by: fugitive
2 Replies
7. Solaris
is x11 and vnc different?
to my knowledge these are used to provide graphical interface to remote machines for the user who would be sitting some where else. i guess i understood the concept correctly? if not please correct me..
---------- Post updated at 09:20 AM ---------- Previous update... (3 Replies)
Discussion started by: chidori
3 Replies
8. UNIX and Linux Applications
I have been having issues with VNC. I have been gettining a lot of errors but mostly gray screens and some black screens. I think this may also be a gnome error. I know that the xstartup file is the file to look at.
> more ~/.vnc/xstartup
#!/bin/sh
&& xrdb $HOME/.Xresources
xsetroot -solid... (0 Replies)
Discussion started by: bitlord
0 Replies
9. Solaris
Hi ,
Everytime after reboot when user tries to start vnc below error is thrown
$ vncserver :5
Couldn't start Xvnc; trying default font path.
Please set correct fontPath in the vncserver script.
Couldn't start Xvnc process.
_XSERVTransSocketCreateListener: failed to bind listener... (7 Replies)
Discussion started by: chidori
7 Replies
10. Linux
Hi,
Is there a way to open vnc:0 on redhat?
Thanks (1 Reply)
Discussion started by: Somename
1 Replies
LEARN ABOUT SUSE
ivman-launch
IVMAN-LAUNCH(8) System Manager's Manual IVMAN-LAUNCH(8)
NAME
ivman-launch - launch script for Ivman
SYNOPSIS
ivman-launch [ --exit-with-session <cmd> ] [ OPTIONS ] [ COMMAND [ ARGS... ]]
DESCRIPTION
ivman-launch is a simple script used to launch Ivman. Its sole purpose is to ensure Ivman is closed at the end of a user's login session.
You can use it if your session manager does not properly close Ivman when you log out.
ivman-launch supports the same command-line options as Ivman, and one additional option: --exit-with-session. Thus, there is no point
using ivman-launch if you do not need to use this option.
If you supply a COMMAND (with optional ARGS), the the specified command will be run after ivman is started, and ivman will be killed after
that command exits.
OPTIONS
--exit-with-session <cmd>
ivman-launch will block until the command 'cmd' terminates, at which point it will kill Ivman and exit itself. If the command 'cmd'
is not running when ivman-launch is started, Ivman will exit immediately. Note that this option implies Ivman will be called with
the '--nofork' option. option.
--debug --nofork --system
These flags be passed to the launched ivman command.
EXAMPLES
ivman-launch --exit-with-session xinit &
The ivman process will be started, then the xinit process is watched. When the xinit process exits, ivman is killed. Placing this
command in an ~/.xinitrc file would cause Ivman to launch in the background when your session begins, and exit when your session
ends:
ivman-launch /usr/bin/x-window-manager
The ivman process is launched, then /usr/bin/x-window-manager is run, when x-window-manager exits, ivman is killed. This is an
example of how ivman might be launched from Xsession in order to chain several programs together in one session.
SEE ALSO
ivman(8) Xsession(5)
CREDITS
This script was written by Daniele Favara.
10 February 2006 IVMAN-LAUNCH(8)