if i wanted to ping all the machines in a given directory (/etc/hosts) and return a total count of responses how would i go about scripting that?
complete newbie...so be gentle
if ; then //$1 = /etc/hosts
cd "$1"
//this puts me into the directory i need...but how do i send ... (2 Replies)
I would have searched for this but I couldn't really think of what to use for the search text...
I've got a situation where I need to automate responses to an executable when running it from a script so that it can be made into a job the operators don't have to interact with. When I run it... (2 Replies)
Unfortunately googling the word 'chat' gives you zebedee billion responses that relate to everything and few of them refer to the linux chat command. I've read the man page and found a couple of examples but can't see how to do this.
I want to query the modem for it's manufacturer, product id... (8 Replies)
Hello,
I am trying to count how many times a subject makes a correct switch or a correct stay response in a simple task. I have data on which condition they were in (here, labeled "IMAGINE" and "RECALL"), as well as whether they made a left or right button response, and whether the outcome was... (5 Replies)
Hello,
I'm looking for an awk one-liner that prints the first two data fields, then contains a conditional where if $3>$4, it prints $3-$4. Otherwise, it prints $3. Example:
Data file:
123,456,999,888
333,222,444,555
654,543,345,888
444,777,333,111
Output:
123,456,111
333,222,444... (2 Replies)
Greetings,
I've got a Zenoss v2.5 server monitoring a large video encoding farm. Needless to say, these systems are under high bandwidth and CPU utilization the majority of the time.
What I'm running into is that, occasionally, these systems will fail to respond to a standard SNMP request,... (1 Reply)
Hey everyone,
Okay, so I've been having some fun with the dig command, and wanted to dig my old school. Two questions came up from this. So I:
dig @8.8.8.8 +recurse njcu.edu ANY
and the result is about 8 records, including the SOA record. One of them is this weird TXT record, and the other is... (1 Reply)
I have two Linux machines, Linux1 and Linux2. They both have two NFS mounts. We'll call them /scratch1 and /scratch2. And they both reside on the same NetApp filer. If I copy a 512Mb file from /scratch1 to /scratch2 while logged on Linux1 it takes 40s. However if I scp this file from... (1 Reply)
So first: Sorry if the title is confusing...
I have a script I'm writing with a file with several names in it (some other info - but it's not really pertinent...) - I want to be allow the user to delete certain records, but I ran into a problem I'm not sure how to go about fixing.
If I were... (6 Replies)
Discussion started by: sabster
6 Replies
LEARN ABOUT SUSE
fields
fields(3pm) Perl Programmers Reference Guide fields(3pm)NAME
fields - compile-time class fields
SYNOPSIS
{
package Foo;
use fields qw(foo bar _Foo_private);
sub new {
my Foo $self = shift;
unless (ref $self) {
$self = fields::new($self);
$self->{_Foo_private} = "this is Foo's secret";
}
$self->{foo} = 10;
$self->{bar} = 20;
return $self;
}
}
my $var = Foo->new;
$var->{foo} = 42;
# this will generate an error
$var->{zap} = 42;
# subclassing
{
package Bar;
use base 'Foo';
use fields qw(baz _Bar_private); # not shared with Foo
sub new {
my $class = shift;
my $self = fields::new($class);
$self->SUPER::new(); # init base fields
$self->{baz} = 10; # init own fields
$self->{_Bar_private} = "this is Bar's secret";
return $self;
}
}
DESCRIPTION
The "fields" pragma enables compile-time verified class fields.
NOTE: The current implementation keeps the declared fields in the %FIELDS hash of the calling package, but this may change in future
versions. Do not update the %FIELDS hash directly, because it must be created at compile-time for it to be fully useful, as is done by
this pragma.
Only valid for perl before 5.9.0:
If a typed lexical variable holding a reference is used to access a hash element and a package with the same name as the type has declared
class fields using this pragma, then the operation is turned into an array access at compile time.
The related "base" pragma will combine fields from base classes and any fields declared using the "fields" pragma. This enables field
inheritance to work properly.
Field names that start with an underscore character are made private to the class and are not visible to subclasses. Inherited fields can
be overridden but will generate a warning if used together with the "-w" switch.
Only valid for perls before 5.9.0:
The effect of all this is that you can have objects with named fields which are as compact and as fast arrays to access. This only works as
long as the objects are accessed through properly typed variables. If the objects are not typed, access is only checked at run time.
The following functions are supported:
new perl before 5.9.0: fields::new() creates and blesses a pseudo-hash comprised of the fields declared using the "fields" pragma into
the specified class.
perl 5.9.0 and higher: fields::new() creates and blesses a restricted-hash comprised of the fields declared using the "fields" pragma
into the specified class.
This function is usable with or without pseudo-hashes. It is the recommended way to construct a fields-based object.
This makes it possible to write a constructor like this:
package Critter::Sounds;
use fields qw(cat dog bird);
sub new {
my $self = shift;
$self = fields::new($self) unless ref $self;
$self->{cat} = 'meow'; # scalar element
@$self{'dog','bird'} = ('bark','tweet'); # slice
return $self;
}
phash
before perl 5.9.0:
fields::phash() can be used to create and initialize a plain (unblessed) pseudo-hash. This function should always be used instead of
creating pseudo-hashes directly.
If the first argument is a reference to an array, the pseudo-hash will be created with keys from that array. If a second argument is
supplied, it must also be a reference to an array whose elements will be used as the values. If the second array contains less
elements than the first, the trailing elements of the pseudo-hash will not be initialized. This makes it particularly useful for
creating a pseudo-hash from subroutine arguments:
sub dogtag {
my $tag = fields::phash([qw(name rank ser_num)], [@_]);
}
fields::phash() also accepts a list of key-value pairs that will be used to construct the pseudo hash. Examples:
my $tag = fields::phash(name => "Joe",
rank => "captain",
ser_num => 42);
my $pseudohash = fields::phash(%args);
perl 5.9.0 and higher:
Pseudo-hashes have been removed from Perl as of 5.10. Consider using restricted hashes or fields::new() instead. Using
fields::phash() will cause an error.
SEE ALSO
base
perl v5.12.1 2010-04-26 fields(3pm)