10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello all,
I have the following line:
xxx|xxxx|xxxx|xxx.xx|xxx
And i insert the values in an array. I am trying to find out if the field of the array (where field=xxx.xx) has the '.' character.
I am using the code below but it doesn't seem to work.
if($field=~ /./)
{
... (3 Replies)
Discussion started by: chriss_58
3 Replies
2. Shell Programming and Scripting
I am reading a file in perl script .. during the debug the $linein value is :
linein : +ASM1,sys,||¬ |3Æqúoü;”ט||
from this line I am getting the tmepuser and password from above :
($tmpuser, $pwd) = ($linein =~ /^$server\s*,\s*(+)\s*,\|\|(.+)\|\|/sm);
I am getting $tmpuser and... (2 Replies)
Discussion started by: talashil
2 Replies
3. Shell Programming and Scripting
I have a question regarding bulding a hash from a file which has below pattern
I thought I could write something like this but clearly my syntax is way off
$/ = "\n\n";
$" = "\n";
open(FILE, file1) || die;
my %keymaster = ( );
while (<FILE>) {
my $topinfo =~... (5 Replies)
Discussion started by: hankooknara
5 Replies
4. Shell Programming and Scripting
I fail to see how below answer is 1? can someone explain this for me?
DB<3> $string = "The cat sat on the mat";
DB<4> $animal = ($string =~ m/The (.*) sat/);
DB<5> print $animal;
1 (2 Replies)
Discussion started by: hankooknara
2 Replies
5. Shell Programming and Scripting
Below program, I do not get why item I am looking for is , instead of .
When I do $#text, i get the right value for $value1, but when I do , i get somsething4, instead of
somsethingxxxxxxxxxxxxxxxxxxx(which is what I am looking for.
when I do , I get empty.. why? what did I do wrong? can you... (2 Replies)
Discussion started by: hankooknara
2 Replies
6. Shell Programming and Scripting
I copy and paste from the book but this thing is not working.
I cannot figure out what is wrong with myline 9.. can someone please tell me
# cat ./sort4.pl
#!/usr/bin/perl -w
use strict;
use warnings;
my $input = shift;
my $output = shift;
open(IN, '<', $input) or die... (4 Replies)
Discussion started by: hankooknara
4 Replies
7. Shell Programming and Scripting
Hello,
pkzipc of a certain zip file yeilds the following in shell
PKZIP(R) Version 6.0 FAST! Compression Utility for AIX
Copyright 1989-2002 PKWARE Inc. All Rights Reserved. Registered Version
PKZIP Reg. U.S. Pat. and Tm. Off. Patent No. 5,051,745
Viewing .ZIP: test.zip
Length... (13 Replies)
Discussion started by: jerardfjay
13 Replies
8. Shell Programming and Scripting
If I use 2 system commands in a script, will one finish before the next one starts? or will it start the first and the second at the same time?
i.e.
system("ps | grep rminer");
system("ls -al | grep 431"); (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
9. Shell Programming and Scripting
When i run my perl/tk script, a perl window pops up behind the GUI window,, can this be hidden????
Also, can the Icon be changed, the Tk icon in every window??? (1 Reply)
Discussion started by: perleo
1 Replies
10. Shell Programming and Scripting
Where can i find solid information about programming in Perl?
Thank you in advance!!!:) (5 Replies)
Discussion started by: SolidSnake
5 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO
csh(1), ps(1), kill(2), sigvec(2)
BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)