Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm using GNU screen on Ubuntu 12.04. I want to create a screen session named "test":
Code:
screen -S test
and then create some screen tabs. On each task, i do some work such as edit a text file, or something else.
In a situation, i have to shutdown my PC, and then return to work in tomorrow. So, i need to save screen session ("test") to disk, and load this session again.
It does not work that way. "Screen" is used to leave running programs when you can logout, but not turn off computer. So it is most useful on remote computer, a server, which is working all the time. Then you can connect to it from your own computer, establish screen session, logout and turn off your own computer.
If you want that behavior, then every program need to known how to store own session (opened files, their state, row where was cursor, etc.), for example some of application from KDE can do it and KDE has own session manager, when you save session (can be automatically when shutdown), you can restore it any time.
Other methods are hibernation and sleep mode. First store your whole machine state, and restore it after power on, but there can be some hardware issues, which prevent use it, and you can only store one session, and cannot change some computer components in meantime. Latter additionally need be connected to power source or UPS, it need small power to sustain machine state.
It does not work that way. "Screen" is used to leave running programs when you can logout, but not turn off computer. So it is most useful on remote computer, a server, which is working all the time. Then you can connect to it from your own computer, establish screen session, logout and turn off your own computer.
If you want that behavior, then every program need to known how to store own session (opened files, their state, row where was cursor, etc.), for example some of application from KDE can do it and KDE has own session manager, when you save session (can be automatically when shutdown), you can restore it any time.
Other methods are hibernation and sleep mode. First store your whole machine state, and restore it after power on, but there can be some hardware issues, which prevent use it, and you can only store one session, and cannot change some computer components in meantime. Latter additionally need be connected to power source or UPS, it need small power to sustain machine state.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.