12-23-2008
Since session information is stores within the process ( and so in memory) there is no solution...unless you opt for less volatile storage
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I know that this is a relative question but can someone give me an idea of what would be considered a high number of context switches?
I am running vmstat and show a cs value of between 5000 and 6000 on a 4 processor system. How can I deduce if this number is high or not?
Also, the timeslice... (2 Replies)
Discussion started by: keelba
2 Replies
2. Filesystems, Disks and Memory
First time so excuse my ignorance please.
I may not be accurately describing the issue.
I have inherited a small lab mostly SUN V120s.
We lost power and are trying to recover.
Nope no backups...
The primary issue I have is 1 box is an Oracle Server.
It has 2 36Gb harddrives.
I am able to... (3 Replies)
Discussion started by: murphsr
3 Replies
3. HP-UX
I am able to get into single user mode as part of the process of resetting a lost root password, but once I am in that mode, my keyboard no longer works. Any ideas on what's wrong? Without the keyboard, I am stuck. (1 Reply)
Discussion started by: richard46
1 Replies
4. Shell Programming and Scripting
here is a data file.
-------------------------------------
KSH, CSH, BASH, PERL, PHP, SED, AWK
KSH, CSH, BASH, PERL, PHP,
BASH, PERL, PHP, SED, AWK
CSH, BASH, PERL, PHP, SED,
KSH, CSH, BASH, PERL, PHP, SED, AWK
-------------------------------------
My desired output is... (2 Replies)
Discussion started by: VTAWKVT
2 Replies
5. UNIX for Advanced & Expert Users
Hi friends,
I have created a patch which I need to apply to two different files. Here the two files have the same functions implementation but placed at different lines. Just because the line numbers are different I can't use the same patch for both, have to make different ones. Is there some... (0 Replies)
Discussion started by: sreejithc
0 Replies
6. Shell Programming and Scripting
Hi,
There's a file with below contents which I have to read based on the input parameter provided by the user.
FILE_ID=1
FILE_FTP_ID=ftp.server1.com
FILE_FTP_USER=user1
FILE_FTP_PASS=pass1
FILE_ID=2
FILE_FTP_ID=ftp.server2.com
FILE_FTP_USER=user2
FILE_FTP_PASS=pass2
FILE_ID=3... (6 Replies)
Discussion started by: dips_ag
6 Replies
7. Shell Programming and Scripting
Hello
I have found some piece of code to verify and then run shell script with root permission from normal user.
see : http://blog.mecworks.com/articles/2006/02/23/bash-scripting-tip-running-a-script-as-root
I have wrote two scripts using this tips.
- one to copy file from server to local... (6 Replies)
Discussion started by: jcdole
6 Replies
8. Shell Programming and Scripting
Could anyone please explain Context Managers in Python with some detailed example or any URL that explains in detail?
Initially tried to get some help from google... but not much satisfied.
Thanks in advance...
Regards,
J (1 Reply)
Discussion started by: scriptscript
1 Replies
9. Shell Programming and Scripting
I wrote this code, questions follow
#! /bin/bash -f
# Purpose - to show how if syntax is used within an awk
clear;
ls -l;
echo "This will print out the first two columns of the inputted file in this directory";
echo "Enter filename found in this directory";
read input;
... (11 Replies)
Discussion started by: Seth
11 Replies
LEARN ABOUT V7
systemd-volatile-root.service
SYSTEMD-VOLATILE-ROOT.SERVICE(8) systemd-volatile-root.service SYSTEMD-VOLATILE-ROOT.SERVICE(8)
NAME
systemd-volatile-root.service, systemd-volatile-root - Make the root file system volatile
SYNOPSIS
systemd-volatile-root.service
/lib/systemd/systemd-volatile-root
DESCRIPTION
systemd-volatile-root.service is a service that replaces the root directory with a volatile memory file system ("tmpfs"), mounting the
original (non-volatile) /usr inside it read-only. This way, vendor data from /usr is available as usual, but all configuration data in
/etc, all state data in /var and all other resources stored directly under the root directory are reset on boot and lost at shutdown,
enabling fully stateless systems.
This service is only enabled if full volatile mode is selected, for example by specifying "systemd.volatile=yes" on the kernel command
line. This service runs only in the initial RAM disk ("initrd"), before the system transitions to the host's root directory. Note that this
service is not used if "systemd.volatile=state" is used, as in that mode the root directory is non-volatile.
SEE ALSO
systemd(1), systemd-fstab-generator(8), kernel-command-line(7)
systemd 237 SYSTEMD-VOLATILE-ROOT.SERVICE(8)