Exceed - Session Persist after shutdown


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Exceed - Session Persist after shutdown
# 1  
Old 06-14-2011
Exceed - Session Persist after shutdown

I'm wondering if it is possible to use Exceed as a remote desktop and have my session persist after I close it down (ala VNC Viewer). I find it annoying to always have to reopen my windows and files when I shut it down.

Thanks!
 
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Delete route so it does not persist after reboot

Solaris 10 I am trying to delete a route using the command: route -p delete 192.0.0.0 192.1.3.254 The route gets delete but for some reason the route pops back up in the routing table after reboot. I also deleted the /etc/inet/static_routes file and the route still persists after reboot.... (6 Replies)
Discussion started by: jastanle84
6 Replies

2. UNIX for Dummies Questions & Answers

PATH settings don't seem to persist across sessions

I recently installed LaTeX on my linux machine and I attempted to add a directory to the PATH as the instructions say to do. They tell me to give the following command: PATH=/usr/local/texlive/2011/bin/i386-linux:$PATH; export PATH After I do this I can use commands such as "pdflatex" anywhere,... (5 Replies)
Discussion started by: TR5
5 Replies

3. Solaris

Difference between the desktop session and console session

what is the difference between desktop session and console session in solaris as i am wondering we use option -text for the former and -nowin for the later (1 Reply)
Discussion started by: kishanreddy
1 Replies

4. UNIX for Dummies Questions & Answers

Script to force Oracle database shutdown when shutdown immediate does not work

I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS). Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies

5. Shell Programming and Scripting

Determining if session is a login session

Besides 'who am i' and 'tty' what commands could be used to determine if a session is interactive as compared to a web process or cron process. Any command should work with the common unix variants. (3 Replies)
Discussion started by: jgt
3 Replies

6. AIX

tuning network parameters : parameters not persist after reboot

Hello, On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command. tunrestore -R is present in inittab in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log ... (0 Replies)
Discussion started by: dantares
0 Replies

7. Solaris

I am not able to login in gnome session and java session in Sun solaris 9& 10

I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Discussion started by: durgaprasadr13
0 Replies

8. Shell Programming and Scripting

Hiding Directories on a Session by Session basis

Hi, Apologies if anyone has read my recent post on the same subject in the Linux forum, just thought actually the solution might more likely come from scripting. Essentially, I am trying to restrict access to directories based on the user's name AND their location on a session-by-session... (3 Replies)
Discussion started by: en7smb
3 Replies

9. Shell Programming and Scripting

sqlplus session being able to see unix variables session within a script

Hi there. How do I make the DB connection see the parameter variables passed to the unix script ? The code snippet below isn't working properly. sqlplus << EOF user1@db1/pass1 BEGIN PACKAGE1.perform_updates($1,$2,$3); END; EOF Thanks in advance, Abrahao. (2 Replies)
Discussion started by: 435 Gavea
2 Replies
Login or Register to Ask a Question
vncserver(1)                                                         TightVNC                                                         vncserver(1)

NAME
vncserver - a wrapper to launch an X server for VNC. SYNOPSIS
vncserver [:display] [-geometry widthxheight] [-depth depth] [-pixelformat rgbNNN|bgrNNN] [-name desktop-name] [Xvnc-options...] vncserver -kill :display vncserver -help DESCRIPTION
vncserver is a wrapper script for Xvnc, the free X server for VNC (Virtual Network Computing). It provides all capabilities of a standard X server, but does not connect to a display for itself. Instead, Xvnc creates a virtual desktop you can view or control remotely using a VNC viewer. OPTIONS
You can add Xvnc options at the command line. They will be added to the invocation of Xvnc without changes. The options provided by the vncserver itself are as follows: :display The display number to use. If omitted, the next free display number is used. -geometry widthxheight Set desktop width and height. -depth depth Set the colour depth of the visual to provide, in bits per pixel. Must be a value between 8 and 32. -pixelformat rgbNNN|bgrNNN Set colour format for pixels representation. The viewer can do the conversion to any other pixel format, but it is faster if the depth and pixel format of the server is the same as the equivalent values on the viewer display. -name string This specifies the name of the desktop. -kill :display Stops the session running on the specified display. -help Prints a short usage notice to stderr. EXAMPLES
vncserver Invokes Xvnc on the next available display and with suitable defaults. vncserver :1 Invokes Xvnc on display :1. vncserver -geometry 800x600 -depth 16 :1 Invokes Xvnc on display :1 with desktop size of 800x600 pixels and color depth of 16 bits per pixel. vncserver -kill :1 Shuts down Xvnc server on display :1. SEE ALSO
Xvnc(1), vncviewer(1), vncpasswd(1), vncconnect(1) AUTHORS
Original VNC was developed in AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people participated in development, testing and support. Man page authors: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>, Tim Waugh <twaugh@redhat.com>, Constantin Kaplinsky <const@tightvnc.com> August 2006 vncserver(1)