Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Exceed - Session Persist after shutdown Post 302530599 by dvd7e on Tuesday 14th of June 2011 11:53:21 AM
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!
 

9 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

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. 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

7. 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

8. 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

9. 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
Plack::Middleware::Session(3pm) 			User Contributed Perl Documentation			   Plack::Middleware::Session(3pm)

NAME
Plack::Middleware::Session - Middleware for session management SYNOPSIS
use Plack::Builder; my $app = sub { my $env = shift; my $session = $env->{'psgix.session'}; return [ 200, [ 'Content-Type' => 'text/plain' ], [ "Hello, you've been here for ", $session->{counter}++, "th time!" ], ]; }; builder { enable 'Session'; $app; }; # Or, use the File store backend (great if you use multiprocess server) # For more options, see perldoc Plack::Session::Store::File builder { enable 'Session', store => 'File'; $app; }; DESCRIPTION
This is a Plack Middleware component for session management. By default it will use cookies to keep session state and store data in memory. This distribution also comes with other state and store solutions. See perldoc for these backends how to use them. It should be noted that we store the current session as a hash reference in the "psgix.session" key inside the $env where you can access it as needed. NOTE: As of version 0.04 the session is stored in "psgix.session" instead of "plack.session". State Plack::Session::State This will maintain session state by passing the session through the request params. It does not do this automatically though, you are responsible for passing the session param. Plack::Session::State::Cookie This will maintain session state using browser cookies. Store Plack::Session::Store This is your basic in-memory session data store. It is volatile storage and not recommended for multiprocessing environments. However it is very useful for development and testing. Plack::Session::Store::File This will persist session data in a file. By default it uses Storable but it can be configured to have a custom serializer and deserializer. Plack::Session::Store::Cache This will persist session data using the Cache interface. Plack::Session::Store::Null Sometimes you don't care about storing session data, in that case you can use this noop module. OPTIONS
The following are options that can be passed to this module. state This is expected to be an instance of Plack::Session::State or an object that implements the same interface. If no option is provided the default Plack::Session::State::Cookie will be used. store This is expected to be an instance of Plack::Session::Store or an object that implements the same interface. If no option is provided the default Plack::Session::Store will be used. It should be noted that this default is an in-memory volatile store is only suitable for development (or single process servers). For a more robust solution see Plack::Session::Store::File or Plack::Session::Store::Cache. BUGS
All complex software has bugs lurking in it, and this module is no exception. If you find a bug please either email me, or add the bug to cpan-RT. AUTHOR
Tatsuhiko Miyagawa Stevan Little <stevan.little@iinteractive.com> COPYRIGHT AND LICENSE
Copyright 2009, 2010 Infinity Interactive, Inc. <http://www.iinteractive.com> This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.12.4 2011-03-29 Plack::Middleware::Session(3pm)
All times are GMT -4. The time now is 08:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy