I am capturing command's output on remote host using Expect. The problem is that the command line arguments also getting print with the output in file and also need to print last two relevant columns (percentage used and its mounted point).
Please wrap all code, files, input & output/errors in CODE tags.
It makes it far easier to read and preserves spaces for indenting or fixed-width/tabulated data.
Hi,
I was wondering if there is an easy way to strip off the required basename. I have a script called apb0110021.sh and the contents of the script are
typeset -u MScript=`basename $0 | cut -d. -f1`
scriptname=sys.Audit.ksh
parms="PROJECT1 dsAudit $MScript 1 BEGIN"
$SCRIPTS/$scriptname... (3 Replies)
Hi Group,
I am struggling to increase buffer size of expect,
sometimes after increasing the buffer size, expect captures all my expected output, sometimes not, :-(
I tried
match_max 700000
set expect_out(buffer) {}
Could anybody guide me for any solution.
HTH,... (1 Reply)
Hi,
I am trying to extract part of a line using "awk". My requirement is to extract the value $6 (which is the last parameter) from a line. As the sixth value contains some space, i am getting only part of the string. so i am trying to extract from $6 to the end of the buffer.
How to do it... (7 Replies)
Hi All,
I have to write one expect script to login to one system.
I am using
set timeout -1
match_max 100000
spawn ssh root@hostname
Now when I do spawn ssh to that host it send some warning message and one challenge
Challenge: 111-2345
I need to read this challenge value and has... (1 Reply)
First, to level set: I'm proficient enough with basic BASH scripting for simple things (say, 4 out of 10), but this current project really requires a higher understanding of EXPECT than I have.
I have an interactive-only control application residing locally on a database server that I would... (2 Replies)
I have the code
message={TP=2012:09:23:00:00:00:GMT,SD=2012:09:23:00:00:00:GMT,SP=2,FT=CCGT,FG=3605}
I want to extract the FG=3605 parts of this. Please help. I am trying to do this using awk or unix. (5 Replies)
I have written an application in Tcl-Expect which spawns minicom and
sends and receives data via the serial port. Sometimes i see that the
application receives control characters along with human readable data.
A search on the internet tells me that the control characters are
nothing but the VT... (0 Replies)
Hi,
I needed to extract some specific characters from a string based on user input. For example: After the script executes the user enters the following details:
Please enter the string: This is a shell script
Please enter the starting position: 11
Please enter the number of characters to be... (4 Replies)
I have a string:
2015-04-16 07:30:05,625000 +0900 xxxx.com
I just want to extract the time from the above line I am using the below syntax
x=~ /(.*) (\d+)\:(\d+)\:(\d+),(.*)\.com/
$time = $2 . ':' . $3 . ':' . $4;
print $time
But it is not working. Can some1 please help (2 Replies)
Discussion started by: karan8810
2 Replies
LEARN ABOUT CENTOS
tmpfs
tmpfs(5) Debian Administrator's Manual tmpfs(5)NAME
tmpfs - variables that configure tmpfs filesystems mounted during boot
DESCRIPTION
The /etc/default/tmpfs file contains variable settings in POSIX format:
VAR=VAL
Only one assignment is allowed per line. Comments (starting with '#') are also allowed.
This file is for the configuration of tmpfs filesystems mounted in early boot, before filesystems from /etc/fstab are mounted. This cur-
rently includes the filesystems /run, /run/lock, /run/shm and /tmp. /run is required to be a tmpfs on systems supporting tmpfs mounts.
/run/lock and /run/shm may be separate tmpfs mounts, useful for enforcing separate size limits. /tmp is not required to be a tmpfs, but is
mounted as a tmpfs by default.
/run Previously configured using RAMRUN in /etc/default/rcS, /run is now always mounted as a ram file system (tmpfs). The size of the
tmpfs can be controlled using TMPFS_SIZE and RUN_SIZE. If desired, the defaults may also be overridden with an entry in in
/etc/fstab, for example:
tmpfs /run tmpfs nodev,nosuid,size=10%,mode=755 0 0
The contents of /run will always be lost on system reboot, and it it is no longer explicitly cleaned at boot. Packages can not
expect directories in /run to exist after boot. Packages expecting this are buggy and need to be fixed. Note that /run was previ-
ously /var/run, and a compatibility symlink or bind mount will be created to allow the old path to continue to function.
/run/lock
Previously configured using RAMLOCK in /etc/default/rcS. Configured using RAMLOCK, TMPFS_SIZE and LOCK_SIZE. If desired, the
defaults may also be overridden with an entry in in /etc/fstab, for example:
tmpfs /run/lock tmpfs nodev,noexec,nosuid,size=52428800,mode=1777 0 0
Note that irrespective of these settings, /run/lock will be located on a tmpfs, either one mounted on /run/lock (if RAMLOCK=yes) or
one mounted on /run (if RAMLOCK=no), and as a result the contents of /var/lock will always be lost on system reboot, and it it is no
longer explicitly cleaned at boot. Packages can not expect directories in /var/lock to exist after boot. Packages expecting this
are buggy and need to be fixed. Note that /run/lock was previously /var/lock, and a compatibility symlink or bind mount will be
created to allow the old path to continue to function.
/run/shm
Previously configured using RAMSHM in /etc/default/rcS. Note that the setting in /etc/default/rcS, if present, will still be used,
but the setting in /etc/default/tmpfs will take precedence if enabled. Configured using RAMSHM, TMPFS_SIZE and SHM_SIZE. If
desired, the defaults may also be overridden with an entry in in /etc/fstab, for example:
tmpfs /run/shm tmpfs nosuid,nodev,size=40%,mode=1777 0 0
Packages can not expect directories in /run/shm to exist after boot. Note that /run/shm was previously /dev/shm, and a compatibil-
ity symlink or bind mount will be created to allow the old path to continue to function. If an fstab entry for /dev/shm exists
instead of /run/shm, then /dev/shm will continue to be used; note that this is only needed for users of newer versions of the Oracle
database, which contain a buggy check for /dev/shm.
/tmp Previously configured using RAMTMP in /etc/default/rcS. Note that the setting in /etc/default/rcS, if present, will still be used,
but the setting in /etc/default/tmpfs will take precedence if enabled. Configured using RAMTMP, TMPFS_SIZE and TMP_SIZE. If
desired, the defaults may also be overridden with an entry in in /etc/fstab, for example:
tmpfs /tmp tmpfs nodev,nosuid,size=20%,mode=1777 0 0
Packages can not expect directories in /tmp to exist after boot.
OPTIONS
The following variables can be set.
Enabling or disabling tmpfs mounts
The following options enable specific mounts (with the exception of /run) to be enabled or disabled. Note that the addition of an entry to
/etc/fstab for any of the following will enable the mount unconditionally, overriding the setting here.
RAMLOCK
Mount /run/lock as a tmpfs (separately from /run). Defaults to yes; set to no to disable (/run/lock will then be part of the /run
tmpfs, if available).
RAMSHM Mount /run/shm as a tmpfs (separately from /run). Defaults to yes; set to no to disable (/run/shm will then be part of the /run
tmpfs, if available).
RAMTMP Mount /tmp as a tmpfs. Defaults to no; set to yes to enable (/tmp will be part of the root filesystem if disabled). /tmp may also
be configured to be a separate mount in /etc/fstab, which will override the RAMTMP setting.
Configuring size limits for tmpfs mounts
The following options configure size limits for tmpfs mounts. Note that the addition of an entry to /etc/fstab will override any of the
limits specified here.
The following _SIZE variables are the maximum size (in bytes) that tmpfs filesystems can use. The size will be rounded down to a multiple
of the page size, 4096 bytes. If no size is set, TMPFS_SIZE will be used as the default.
More complex mount options may be used by the creation of a suitable entry in /etc/fstab. For example:
tmpfs /run tmpfs size=10% 0 0
is equivalent to
RUN_SIZE=10%
and will override the RUN_SIZE setting. This will allow additional options such as nr_blocks and nr_inodes to be used, and also adjustment
of the mode, nodev, nosuid, noexec options should any change from the defaults be necessary.
TMPFS_SIZE
Maximum size for all tmpfs filesystems if no specific size is provided. The default is 20%VM (20% of virtual memory, including swap
space). If no value is provided here, the kernel default (50% RAM) will be used. Note that the "%VM" suffix may be used in this
and all the _SIZE settings below, but may not be used in /etc/fstab (the absolute size is calculated by the init scripts).
RUN_SIZE
Maximum size of /run (was previously /var/run). The default is 10% core memory; the size required varies widely depending upon the
demands of the software being run; this heuristic scales /run usage on system size. Samba in particular has been seen to use at
least 50MiB in a large heavily used server. Typical usage is hundreds of KiB, maximum is tens of MiB.
LOCK_SIZE
Maximum size of /run/lock (was previously /var/lock). Defaults to 5242880 (5 MiB). Typical usage: tens of KiB; maximum hundreds of
KiB. The default of 5 MiB should ensure the limit is never reached.
SHM_SIZE
Maximum size of /run/shm (was previously /dev/shm). No default size; the size required varies widely depending upon the demands of
the software being run.
TMP_SIZE
Maximum size of /tmp. No default size.
Emergency overflow /tmp
If the amount of free space on the root filesystem falls below a certain size, a tmpfs will be mounted on /tmp (irrespective of the RAMTMP
setting, which this overrides). This is to permit logins when there would otherwise be too little free space for this to be possible.
TMP_OVERFLOW_LIMIT
Mount a tmpfs on /tmp if the amount of free space on the root filesystem is below the specified limit at boot time (default 1024
KiB).
AUTHOR
Roger Leigh <rleigh@debian.org>
SEE ALSO mount(8), rcS(5).
18 Feb 2012 tmpfs(5)
06-07-2019
