Mark Post wrote:
count=$(wc -l /var/log/toolarge | cut -f1 -d )
let start=$count-
if [ ${start} -le 1 ]; then
echo start is set to 1
let start=1
fi
start=$((count 1 ? count - 1 : 1))
like c.
- Larry
--
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Rich Smrcina
Sent: Tuesday, September 04, 2007 8:21 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Trimming a File
Because wc prints the filename in the output:
[EMAIL PROTECTED]:~ wc -l x.xxx
10
Mark gave a nice concise answer to a question for a (hopefully) real
world problem.
Although I'm sure he appreciates the input, I think his methodology has
been picked apart long enough. The question was answered let's move on,
sheesh!
McKown, John wrote:
But it is more efficient to
wc -l
Thanks for the replies to my previous question.
Our network folks have configured their 6509 connection to our OSAs with 1
vlan - 147.
If I define my VSWITCH with a default VLAN ID of 147 and then grant
IPSTACK vlan 147 - all is OK - I can PING etc.
However if I define the VSWITCH with a
What release of VM on you on? In 5.3.0, we separated the default VLAN and
the native VLAN. Prior to 5.3.0, the default VLAN is the same as the
native VLAN. In this case, defining the VSWITCH to default to VLAN 147
means that 147 is the native VLAN (or untagged set). Most likely, the
OSA card
how have you configured the PORTTYPE on the vswitch? Access or trunk? If it's
an access port what you show makes senses. If you want to use a vlan on IPSTACK
how have you set this up, VCONFIG command?
David
-Original Message-
From: Linux on 390 Port on behalf of Peter Rothman
Sent: Wed
In 5.3.0, we separated the default VLAN and
the native VLAN. Prior to 5.3.0, the default VLAN is the same as the
native VLAN. In this case, defining the VSWITCH to default to VLAN
147
means that 147 is the native VLAN (or untagged set). Most likely,
the
OSA card is plugged into an access
According to the network folks the OSA card is plugged into a trunk port
and the native VLAN id is 147.
We are on z/VM 520 so as you say the default VLAN must be the same as the
native VLAN.
Thanks.
Tracy J Adams
[EMAIL PROTECTED]
om
I have
'CP set vswitch vswp1 grant IPSTACK vlan 147'
and the following in the profile for IPSTACK
DEVICE ETH0 OSD 1000
LINK ETH0 QDIOETHERNET ETH0 MTU 1500
HOME
172.31.147.10/24 ETH0
GATEWAY
DEFAULTNET 172.31.147.250 ETH0 1500
David Kreuter
[EMAIL
David says it better than I did. The point I was attempting to make is
that prior to 5.3.0, the default VLAN on the Virtual Switch is the same as
the native VLAN id and should match your physical switches native VLAN. I
assumed the guest on the VSWITCH was not tagging the frames. When you get
Background: in a predominently zOS sysplex environment (2 z9's) and a fairly
large Open Systems environment (Linux, Solaris, AIX, Windoz), a recent storage
subsystem consolidation/upgrade decision was made to purchase an Hitachi
USP1100 on a large tiered storage platform.
Problem : with zVM
My apologies - I see the TCPIP LINK statement has a VLAN option.
Is there a way to specify the VLAN for Linux? We are on
Linux version 2.6.16.21-0.8-default ([EMAIL PROTECTED]) (gcc version 4.1.0
(SUSE Linux))
David Kreuter
[EMAIL PROTECTED]
urces.com
vconfig from candelatech should be on your linux distro from suse. Also go to
http://www.candelatech.com/~greear/
David
-Original Message-
From: Linux on 390 Port on behalf of Peter Rothman
Sent: Wed 9/5/2007 10:19 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Another VSWITCH question
My
I'd like to run a dynamic routing protocol on my lpar base Red Hat Linux
(no z/VM). I want to setup hypersockets and direct some host addresses
through the hypersocket interface, everything else out the OSA. I could
probably set up static addresses for the host but I'd prefer OSPF.
I downloaded
Thanks.
Am I correct in assuming that to use more than 1 vlan on a vswitch you have
to :
For a VM IP stack use the VLAN option on the LINK statement and
For Linux use something like vconfig mentioned below?
David Kreuter
[EMAIL PROTECTED]
urces.com
On Wednesday, 09/05/2007 at 10:20 EDT, Peter Rothman
[EMAIL PROTECTED] wrote:
My apologies - I see the TCPIP LINK statement has a VLAN option.
Is there a way to specify the VLAN for Linux? We are on
Linux version 2.6.16.21-0.8-default ([EMAIL PROTECTED]) (gcc version 4.1.0
(SUSE Linux))
On Wed, Sep 5, 2007 at 10:46 AM, in message
[EMAIL PROTECTED], Bauer, Bobby
(NIH/CIT) [E] [EMAIL PROTECTED] wrote:
I'd like to run a dynamic routing protocol on my lpar base Red Hat Linux
(no z/VM). I want to setup hypersockets and direct some host addresses
-snip-
Before I start jumping
quagga is there. I'll install it and see what goes. What a name!
Thanks
Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474
-Original Message-
From: Mark Post [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 05, 2007
On Wed, Sep 5, 2007 at 11:47 AM, in message
[EMAIL PROTECTED], Bauer, Bobby
(NIH/CIT) [E] [EMAIL PROTECTED] wrote:
quagga is there. I'll install it and see what goes. What a name!
From http://en.wikipedia.org/wiki/Quagga :
The quagga is an extinct subspecies of the plains zebra, which was once
On Wed, Sep 5, 2007 at 10:19 AM, in message
[EMAIL PROTECTED],
Peter Rothman [EMAIL PROTECTED] wrote:
My apologies - I see the TCPIP LINK statement has a VLAN option.
Is there a way to specify the VLAN for Linux? We are on
Linux version 2.6.16.21-0.8-default ([EMAIL PROTECTED]) (gcc version
Thanks Alan/Mark,
What am I trying to do? -
Well I have a LPAR with z/VM 520. We have some production Linux systems and
a few 'test sand boxes' for us to play with.
I have always had 2 access ports via 2 OSA cards to 2 6509s. I have just
been given 2 trunk port connections via 2 new OSA cards
With one vswitch connected to two osa's you can get failover.
If the physical switches are on two different vlans for test/production you can
mimic this on one vswitch by using the same two vlans, one on production the
other sandbox. The vlan spec guarantees data isolation and separation and
Bennie,
We use ShadowImage to replicate VM volumes on a USP 600. I don't know
what differences there may be between a 600 and an 1100. ShadowImage
makes full volume copies, using ICKDSF PPRC commands. We have no
problem issuing the commands from VM. Hitachi also offers something
called
Bennie, I believe you have the have the storage subsystem feature before
the VM flashcopy command will work. I know that when you have DirMaint
and you set it up to use flashcopy it will revert back to DDR unless you
are on DASD subsystems that support Flashcopy.
Thanks,
Gary L. Detro
Senior
On Tuesday, 09/04/2007 at 10:45 EDT, Rick Troth [EMAIL PROTECTED] wrote:
I cannot offer MONEY to the IBM team(s) which support 31-bit
Linux for S/390. But to abandon a platform is counter to
the whole effort behind Linux. (Not that platforms aren't lost.)
Huh? I thought Linux was about
On Sep 5, 2007, at 10:41 AM, Alan Altmark wrote:
If IBM actively encouraged distributors to build and ship an S/390
version
of the new distros, while at the same time not supporting any of
its own
software on it, the message would be, umm, mixed at best;
misleading at
worst. And I'm not sure
Thanks to all that helped. I had in one place set a
profile and in another su to the instance.
Again, thank all of you for the help.
Mace
--- John Summerfield [EMAIL PROTECTED]
wrote:
LJ Mace wrote:
I'm trying to finish a script that will bring
down/backup/zip/restart our database and
Next time tell them to verify the volume noverify is
VERY dangerous as you(he) found out.
Mace
--- Little, Chris [EMAIL PROTECTED] wrote:
well sort of. our intrepid storage person ran the
jcl at the end of
this email to initialize dasd. to my chagrin, it
included the three
physical volumes
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of LJ Mace
Sent: Wednesday, September 05, 2007 1:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: trashed 3390-9
Next time tell them to verify the volume noverify is
VERY dangerous as you(he) found
I was unsuccessful in getting this script to work. However, that could have
been because all ftp traffic from my Linux system's IP Address was blocked at
the firewall. After that restriction was lifted, I tried and successfully
transmitted a file via ftp over ssl using curl. It worked
On Wed, 2007-09-05 at 08:38 +0800, John Summerfield wrote:
Mark Post wrote:
On Tue, Sep 4, 2007 at 2:21 PM, in message
[EMAIL PROTECTED], Scully, William P
[EMAIL PROTECTED] wrote:
What's the best technique for trimming a file?
I thought one of the requirements was that the file itself
31 matches
Mail list logo
