Bastille

Bastille

[Scott Howell]

Speakup friends,

I decided to try out Bastille. Its quite good and seems to be really
indepth and if you want to learn a bit on firewalling while setting it
up, its the poop as far as I can tell. Ok, well it would be if I could
get it configured. I'm having some problems with the perl scripts. I
can't captured the errors its generating in the scripts cause they just
scroll off the screen. Is there a way to capture these? The error log it
generates isn't giving me any useful data. I suspect there is something
being called in the script I just don't have installed, but I don't know
what. I ran it on another Debian box that has lots of stuff installed,
but I was trying to keep things minimized on the intended firewall box. I
assume correctly or incorrectly, that apt-get would have gotten all the
dependancies covered, but obviously not.

Any thoughts welcome cause I'm going nuts. I'm there you know, near the
final steps of getting the thing configured and it craps out.

DAMN!!!!

tia

Scott

Re: Bastille

[Geoff Shang]

On Sat, 28 Sep 2002, Scott Howell wrote:

> can't captured the errors its generating in the scripts cause they just
> scroll off the screen. Is there a way to capture these? The error log it
> generates isn't giving me any useful data.

You can do this by redirecting standard error, either to standard out or to
a file.  Some examples:

<command> 2>&1
redirects standard error to standard output.  This means you can do
commands like:
<command> 2>&1 |more
or
<command> 2>&1 >filename.log

to capture everything.  This is mainly useful when you need to see errors
in context, such as with a compilation.

If you only want to log the errors, you can do:
<command> 2>filename.log

Using this logic, you can make a program only display the errors with no
regular output by doing
<command> >/dev/null

since you've only redirected standard output, standard error will still be
seen.

Hope this helps.

Geoff.

Re: Bastille

[Janina Sajka]

Haven't tried using Bastille in a year or two. Are you running it in lynx? I recall that it wasn't easy to track, though
I did successfully get it going back then.

You might want to read through the scripts to see exactly what's happening.

Frankly, it's probably a better idea to strip out all the scripting and just follow the script narative by hand. That
way, you'll know what files are being modified and how. My problem, when I ran Bastille, was that I didn't do that, so
had trouble later because I lost control of what was being set from what config file.


Sorry, don't think I'm being of much help to you.

Scott Howell writes:
> From: showell@lrxms.net (Scott Howell)
> 
> 
> Speakup friends,
> 
> I decided to try out Bastille. Its quite good and seems to be really
> indepth and if you want to learn a bit on firewalling while setting it
> up, its the poop as far as I can tell. Ok, well it would be if I could
> get it configured. I'm having some problems with the perl scripts. I
> can't captured the errors its generating in the scripts cause they just
> scroll off the screen. Is there a way to capture these? The error log it
> generates isn't giving me any useful data. I suspect there is something
> being called in the script I just don't have installed, but I don't know
> what. I ran it on another Debian box that has lots of stuff installed,
> but I was trying to keep things minimized on the intended firewall box. I
> assume correctly or incorrectly, that apt-get would have gotten all the
> dependancies covered, but obviously not.
> 
> Any thoughts welcome cause I'm going nuts. I'm there you know, near the
> final steps of getting the thing configured and it craps out.
> 
> DAMN!!!!
> 
> tia
> 
> Scott
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Re: Bastille

[Scott Howell]

Thanks, I neglected perhaps to mention the problem at hand. Capturing the
error might be simple enough, but in order to get them I need to actually
go through the interactive script. I assume these methods you mentioned
would not allow this?

tnx

I did listen to the output again and see its some backend script or
something that's crapping out.

Re: Bastille

[Scott Howell]

Janina,

I don't know if or how much was done in perl, but I know that portion of
it is way_beyond me. I'll have to attempt to pull it apart and see what I
can do with it.
I will say that it was very easy to setup once I realized the answers
like yes and no were set by the arrows keys and you could determine which
was the active answer by moving the Speakup review keys to the yes or no
and if it was black on white, it was set as the slected or active answeer
and if white on black was unselected.
Actually the tab key stepped you through the questions. Worked well until
it barfed on the last leg of implementing the changes. Got to get a
handled on that part of it. I'll ask the package maintainer if nothing
else to explain what's happening and maybe I'll get it straight.

tnx

Re: Bastille

[Janina Sajka]

I have a vague recollection that a running log of actions is preserved by the installation script. There's usually a
Bastille directory at the / level, or maybe in /root.

Again, this is my recollection, and it's been awhile.

Scott Howell writes:
> From: showell@lrxms.net (Scott Howell)
> 
> Thanks, I neglected perhaps to mention the problem at hand. Capturing the
> error might be simple enough, but in order to get them I need to actually
> go through the interactive script. I assume these methods you mentioned
> would not allow this?
> 
> tnx
> 
> I did listen to the output again and see its some backend script or
> something that's crapping out.
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Re: Bastille

[Geoff Shang]

On Sat, 28 Sep 2002, Scott Howell wrote:

> Thanks, I neglected perhaps to mention the problem at hand. Capturing the
> error might be simple enough, but in order to get them I need to actually
> go through the interactive script. I assume these methods you mentioned
> would not allow this?

They might or might not.  In such cases, you might want to try the script
command.

Geof.

Re: Bastille

[shaun_oliver]

scott,
use script filename
then run the bastil app and then when it craps out type exit to exit the
script session and then u can go through that file u created with the
script command.

-- 
Shaun Oliver


In a world without fences
          and walls who needs Windows and Gates?

EMAIL: shaun_oliver@optusnet.com.au
ICQ: 76958435

Re: Bastille

[Scott Howell]

Thanks Geof,

Will have a look.

Re: Bastille

[Steve Holmes]

Another idea that just come to me, try the script command.

First, type script and hit enter.
Then run the bastille script like you have been; the output you see on
the screen is also being captured in a default file name of
typescript.  When finished with it, just "close" the current shell.
What I mean is the script command actually opens up a subshell to run
the next command you entered.  Do a "man script" for more details.  I
find this to be extremely powerful!

On Sat, Sep 28, 2002 at 11:06:40PM -0400, Scott Howell wrote:
> Thanks, I neglected perhaps to mention the problem at hand. Capturing the
> error might be simple enough, but in order to get them I need to actually
> go through the interactive script. I assume these methods you mentioned
> would not allow this?
> 
> tnx
> 
> I did listen to the output again and see its some backend script or
> something that's crapping out.
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

Re: Bastille

[Scott Howell]

Steve,

Yes, I did and its most useful. Excellent ideas and advice from folks on
here.

Thanks much good people.

Scott