Sponsored Content
Full Discussion: swap displays differently
Operating Systems Solaris swap displays differently Post 302255348 by incredible on Thursday 6th of November 2008 09:40:20 AM
Old 11-06-2008
hi vimes, i don have the access to system at the moment will see to get the output.
jlliagre, I did explain the same to my client but he was not satisfied with my answer.. I also checked across the other systems and did compare...
if the prtvtoc is configured with 16G, the df -k output for swap is also around 16G, which mounts on /tmp, /var/run , /etc/svc/volatile..

But on this system, swap for /tmp, /var/run , /etc/svc/volatile shows around 30G.. That's why feeling wierd..Smilie
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Why does cron run this differently?

test.ksh =================== #!/usr/bin/ksh APPLICATION=hr_app APPLICATION_UPPER=`echo $APPLICATION | tr ` echo $APPLICATION_UPPER > /tmp/test.txt echo $APPLICATION >> /tmp/test.txt which tr >> /tmp/test.txt =================== When I run this from the shell: /home/natter> more... (6 Replies)
Discussion started by: natter
6 Replies

2. Shell Programming and Scripting

Script behaving differently in Crontab..

Hi, I wrote a script to stop a process,truncate its log files and re-start the process... We are using Progress Software in Unix ( Sun Sparc) When ever I start this progress program , it should kick off a C pgm in the background.. The script work perfectly fine when I run it from command... (4 Replies)
Discussion started by: newtoxinu
4 Replies

3. Solaris

Swap config - Mirror swap or not?

Hello and thanks in advance. I have a Sun box with raid 1 on the O/S disks using solaris svm. I want to unmirror my swap partition, and add the slice on the second disk as an additional swap device. This would give me twice as much swap space. I have been warned not to do this by some... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

4. Shell Programming and Scripting

Why does IF loop behave differently in different shells

Hi , I have a script that compares two string and prints the larger string , This is an extract of a biggers script that i have. #! /bin/ksh DT_STRING_CMP=20081221223440 DT_STRING=20071221223440 if ; then echo "20081221223440" fi echo... (1 Reply)
Discussion started by: amit1_x
1 Replies

5. Shell Programming and Scripting

Why does IF loop behave differently in different shells

Hi , I have a script that compares two string and prints the larger string , This is an extract of a biggers script that i have. #! /bin/ksh DT_STRING_CMP=20081221223440 DT_STRING=20071221223440 if ; then echo "20081221223440" fi echo... (5 Replies)
Discussion started by: amit1_x
5 Replies

6. UNIX for Dummies Questions & Answers

formatting differently in last loop

hi. i'm trying to create a list users that is formatted for an SQL query. it should take the form: 'user1', 'user2', 'user3'as you can see, there is no comma after the last value. could someone help me revise my code to do this? while read user; do print "'"$userid"'," >>... (3 Replies)
Discussion started by: ankimo
3 Replies

7. HP-UX

Swap device file and swap sapce

Hi I have an integrity machine rx7620 and rx8640 running hp-ux 11.31. I'm planning to fine tune the system: - I would like to know when does the memory swap space spill over to the device swap space? - And how much % of memory swap utilization should be specified (swap space device... (6 Replies)
Discussion started by: lamoul
6 Replies

8. Solaris

Explain the output of swap -s and swap -l

Hi Solaris Folks :), I need to calculate the swap usage on solaris server, please let me understand the output of below swap -s and swap -l commands. $swap -s total: 1774912k bytes allocated + 240616k reserved = 2015528k used, 14542512k available $swap -l swapfile dev swaplo... (6 Replies)
Discussion started by: seenuvasan1985
6 Replies

9. Shell Programming and Scripting

Why awk perform differently when using variable?

Hi Gurus, I hit a hard block in my script. when using awk command with variable, I got different result. Please see below: my test file as below: $ cat demofile.txt filename-yyyy-abcd filename-xxx-week-pass filename-xxx-week-run for testing purpose, I put 3 awk command in one script.... (7 Replies)
Discussion started by: ken6503
7 Replies

10. UNIX for Beginners Questions & Answers

'Connect' behaves differently on Solaris 11

Our application fails to run successfully on Solaris 11. The same works fine in Solaris 10. Due to which we are unable to migrate to Solaris 11. The app basically involves forking a child process, which finally connects with parent process. But on Solaris 11, it is unable to connect with parent... (0 Replies)
Discussion started by: wini008
0 Replies
SYSTEMD-FSTAB-GENERATOR(8)				      systemd-fstab-generator					SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 06:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy