06-08-2011
Help in Understanding ISMP
Hi,
Good day to everyone.
This is my first time joining the community and wanted to say thanks in advance for all your help and assistance. First, I am not expert in AIX and UNIX but I do know a thing or two and I have a simple question regarding ISMP.
We are using AIX 5.3 and a couple of days ago our UNIX filesystem /tmp used 100% of the diskspace allocated to it and when we investigated it, there was a lot of 'ismp001, ismp002, ismp003...ismp10001, ismp, 10002, etc., which is being created every 5 minutes.
Firstly, I wanted to understand what the ismp is for (I searched and saw its from InstallShield) and why is it placing an entry in the /tmp directory?
The solution that we did was determining the UNIX user who is creating the directory and once we got the user, I did a ps -ef|grep user and saw a lot of <defunct> and processes in square brackets [ ], so we did a cleanup (kill) of these processes which then stopped the creation of the ismp folder.
Would anyone know whether there are other processes (aside from installation) may create an ismp folder?
Thanks in advance.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I just started shell coding and I'm a bit confused on how 'mv' works can someone explain to me how it works and if i did this correctly. Thanks.
echo "Enter Name of the first file:"
read file1
#echo $file1
if ; then
echo "Sorry, file does not exist."
exit 1
... (16 Replies)
Discussion started by: taiL
16 Replies
2. Shell Programming and Scripting
# sub: find block (in cols), return line-numbers (begin-end) or 0 if notfound
sub findb{
my ($exp1,$col1,$exp2,$col2)= @_; # $exp = expression to find, $col - column to search in
my $cnt=0;
my ($val1,$val2);
my ($beg,$end);
for($cnt=1;$cnt<=65536;$cnt++){
$val1 =... (3 Replies)
Discussion started by: suvenduperl
3 Replies
3. UNIX for Dummies Questions & Answers
Hi Gurus:
I am trying to understand the following line of code.I did enough of googling to understand but no luck.Please help me understand the follow chunk of code:
X=$0
MOD=${X%/*}/env.ksh
X is the current script from which I am trying to execute.
Say if X=test.ksh
$MOD is echoing :... (3 Replies)
Discussion started by: vemana
3 Replies
4. Shell Programming and Scripting
Hi all
I stuck with a problem. I want to understand the execution of the below code. Can any one please help me
`sqlplus username/passwd@DB << EOF
set serveroutput on
declare
begin
sql_query;
end;
/
commit
/
quit
EOF`
My ques is why do we use EOF and how does it help. (4 Replies)
Discussion started by: parthmittal2007
4 Replies
5. Shell Programming and Scripting
Hi Guys,
I am new to scripting , I am trying to rebuild a script based on an old script. Can someone help me figure out what the script is doing? This is only a part of the script.
I am looking to interpret these two points in the scripts:-
1)
test=`echo $?`
while
I do not... (3 Replies)
Discussion started by: rajsan
3 Replies
6. Shell Programming and Scripting
Hi, I saw the following explanation about alias in bash from gnu website, but I didn't get the meaning:
Bash always reads at least one complete line of input before executing any of the commands on that line.
Aliases are expanded when a command is read, not when it is executed. Therefore, an... (3 Replies)
Discussion started by: Roy987
3 Replies
7. UNIX for Dummies Questions & Answers
I tried to use lseek system call to determine the number of bytes in a file. To do so, I used open system call with O_APPEND flag to open a file. As lseek returns the current offset so I called lseek for opened file with offset as zero and whence as SEEK_CUR. So I guess it must return the number of... (3 Replies)
Discussion started by: Deepak Raj
3 Replies
8. AIX
Hello all,
I've been asked to help with some cleanup on a couple of systems that were running some Websphere apps. I need to remove the following filesets:
mqsi61.cfgmgrc 6.1.0.2 COMMITTED Config. Manager Component
mqsi61.cfgmgrf 6.1.0.2 COMMITTED Config.... (4 Replies)
Discussion started by: ZekesGarage
4 Replies
9. Shell Programming and Scripting
Hi,
I found this in a script and I would like to know how this works
Code is here:
# var1=PART1_PART2
# var2=${var1##*_}
# echo $var2
PART2
I'm wondering how ##* makes the Shell to understand to pick up the last value from the given. (2 Replies)
Discussion started by: sathyaonnuix
2 Replies
LEARN ABOUT DEBIAN
birthday
birthday(1) General Commands Manual birthday(1)
NAME
birthday - warn about upcoming birthdays and other events
SYNOPSIS
birthday [-w|-c] [-f file] [-W defwarn] [-M maxwarn] [-m minwarn] [-l lines] [-p weeks] [-d total] [-i width]
DESCRIPTION
The birthday command reads a file, by default ~/.birthdays, which gives a list of events in the near future (see section FILE FORMAT for
details). It can then produce either a list of events which are coming up within the next few weeks, or a text-based calendar with a few
lines for each day.
OPTIONS
-w Display a list of upcoming events. This is the default.
-c Display a calendar, designed to be piped to lpr(1).
-f file
Read the events from file rather than ~/.birthdays. If file is a single hyphen, read the events from the standard input (usually
the terminal).
List Options
-W warn
Warn warn days in advance, for entries that have no w flag (see FILE FORMAT). If this switch is not specified, it defaults to 21
days.
-M max Warn at most max days in advance. This overrides any flag given in the file.
-m min Warn at least min days in advance. This overrides any flag given in the file.
Calendar Options
-l lines
Print lines lines for every day.
-p weeks
Print weeks weeks on every page of the calendar. If set to 0, the default, disables page breaks.
-d days
Print the calendar for up to days days in advance.
-i width
Print the calendar width characters wide. This affects the length of the lines separating each day, and the point at which events
will be word-wrapped.
FILE FORMAT
Each line beginning with a hash sign, `#', is a comment and will be ignored. Lines beginning with an ampersand, `&', are directives. Cur-
rently there is only one such directive, &include file, which reads in a seperate file from your .birthdays file. file should be given
with an absolute path, which should not use the tilde notation to specify your home directory.
Any other line specifies the name of a person or event, followed by an equals sign and a date (DD/MM, DD/MM/YY or DD/MM/YYYY, where the
form DD/MM/YY is assumed to give a date in the 20th century and is now deprecated), and finally some extra options. These options are:
bd This line is a birthday (the default). The year, if given, should be when the person was born. A line designated as a birthday will
produce output like Erin has a birthday in 3 days' time or Jemima is 3 in 2 weeks' time.
ann This line is an anniversary. The year, if given, should be the year in which the thing happened, producing output like Pen exploded
3 years ago tomorrow given a line such as Pen exploded=12/09/93 ann.
ev This line is an event of some sort. If a year is given, the text will be displayed in that year only; otherwise, it will be dis-
played every year. The remaining time is simply appended to the text; for instance, the input Easter=7/4/1996 ev would give rise to
the text Easter in 1 week's time.
wn Warn n days in advance of the date, rather than the default of 21 days or the number given with the -W flag.
todate The event lasts until date, which should be in the same format as for the date of the event.
fordays
The event lasts for days days.
DATE SPECIFICATION
The file format documented here handles dates in a couple of slightly non-standard ways. Firstly, the dates are given in British format of
DD/MM/YYYY, as opposed to the more normal US format MM/DD/YYYY.
Secondly, dates with a two-digit year are assumed to be in the 20th century (19xx), rather than taking the standard convention of assuming
all two-digit years less than 70 are in the 21st century. This is for reasons of compatibility with older data files, since many people
have birthdays before 1970, and the program was written before I came across the Y2K issues. :-( You should probably avoid this format.
EXAMPLE
Joe Blow=25/04/1974
FILES
~/.birthdays
Your default birthdays file.
SEE ALSO
cal(1)
BUGS
Both the "features" in the DATE SPECIFICATION section could be construed as bugs, and are mostly present for backwards compatibility.
The calendar mode should be a seperate program.
The program cannot warn more than one year in advance of anything.
AUTHOR
Andy Mortimer <andy.mortimer@zetnet.co.uk>
birthday(1)