From: Anthony Liguori <aliguori@us.ibm.com>
To: Scott Parish <srparish@us.ibm.com>
Cc: Matt Ayres <matta@tektonic.net>, xen-devel@lists.sourceforge.net
Subject: Re: [PATCH] warn when iproute2 or bridge-utils are missing
Date: Fri, 25 Feb 2005 15:48:08 -0600 [thread overview]
Message-ID: <421F9D18.8000300@us.ibm.com> (raw)
In-Reply-To: <20050225211946.GB11704@us.ibm.com>
Isn't it more appropriate to have these be install-time checks?
It seems wasteful to check for an installed program every time a script
is run. I submitted check scripts for iproute2 and iptables a while ago.
All you have to do is add a check_iproute2 script to the tools/check
directory that basically looks like:
#!/bin/sh
which ip || (echo "Check for iproute2 failed && exit 1)
Regards,
Anthony Liguori
Scott Parish wrote:
>On Fri, Feb 25, 2005 at 03:22:58PM -0500, Matt Ayres wrote:
>
>
>
>>On Fri, 2005-02-25 at 19:08 +0000, Scott Parish wrote:
>>
>>
>>>The attached patch checks for "ip" and "brctl" in the path, and warns
>>>the user if they are not found.
>>>
>>>
>>>
>>Now that the routed setup is included (and IMHO works a whole lot
>>better) shouldn't the brctl check be optional somehow?
>>
>>
>
>Maybe what i started to do would be better then: make sure that output
>from the scripts gets sent to the console in addition to getting buried
>in the log file. Then have the scripts check that the programs that they
>need are available (before fiddling with the network and putting it in a
>half way state).
>
>sRp
>
>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-02-25 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 19:08 [PATCH] warn when iproute2 or bridge-utils are missing Scott Parish
2005-02-25 20:22 ` Matt Ayres
2005-02-25 21:21 ` Scott Parish
2005-02-25 21:48 ` Anthony Liguori [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=421F9D18.8000300@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=matta@tektonic.net \
--cc=srparish@us.ibm.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.