Hello Guys,

I'm new on this list and this is my first post! Let me introduce myself: my
name is Antonio Carlos and I'm Brazilian. I'm a SysAdmin with specialty in
Linux/UNIX, working professionaly with Linux/*BSD platforms since 2003
(mainly Slackware/OpenBSD), but I'm on Linux since 2.0.12 kernel.

I'm always writing scripts, since basic to complex ones. As my current job
in a Check Point reseller, my routine is based in Firewalls migration, so I
wrote a modular script (I call it as Tabajara Migrator) that helps me a lot
in this task. Basically it reads and parses an input file (FortiGate
backup, ASA backup, ISA Server XML, IPTables dump and OpenBSD's Packet
Filter dump), convert it to a pseudo Firewall in a database (MySQL) and
export it to a desired Firewall (currently, it supports only Check Point).
It is completely written in Bash/AWK/SED (ok, one line of Perl) and
currently it have around 7500 lines (distributed in various modules). I'm
working in a little bit of inteligence in this script (such remove
duplicate rules and keep rules with high usage on top).
Who is using it? Me and my co-workers!

On Tue, Nov 18, 2014 at 12:12 PM, Adam Moskowitz <ad...@menlo.com> wrote:

> On the way home from LISA '14 I found myself already thinking about what
> I'm going to submit to next year's conference and about what I'm going
> to contribute to the community between now and then. I have some ideas
> about what I want to do but my inner sysadmin is screaming at me to
> first make sure I understand the problem before I design a solution.
> With that in mind, I'm asking everyone who reads this to take a moment
> and answer a few questions for me.
>
> I believe that many *nix sysadmins write programs (or "scripts," if you
> prefer -- for this discussion the distinction doesn't matter). Maybe
> it's this simple:
>
>         #!/bin/bash
>         cd /home
>         du -ks * | sort -n | head -10
>
> and you wrap that in a cron job, or maybe it's a 200 line Perl program
> that does something more complicated. If you're not writing programs
> that's OK but I want to hear from the people who are writing them.
>
> Would you please take a few moments to send me a description of the
> programs you've written in the last 3 or 6 or 12 months? Specifically,
> would you please send me the following:
>
>         * language used
>         * number of lines
>         * very brief description (< 140 chars? :-) of what
>           the program does
>         * who runs the program:
>             1) you, from the command line
>             2) people in your group, from the command line
>             3) people outside your group, from the command line
>             4) "the system" via anything from cron to whatever
>                config management system you use
>             5) it's a web app
>             6) other
>
> Here's an example:
>
>         perl, 1363 lines
>         simple unit test harness for CLI tools
>         run by: 1 (me, from the command line)
>
> Please reply directly to me. I will NOT distribute or publish this data
> in any way -- I just want to know what kind of programs people here
> write. Your answers won't even appear in a "highly anonymized form" in
> anything I write; this is 100% "background" information that I'll use to
> help me decide what to do.
>
> Thanks,
> Adam
> _______________________________________________
> Tech mailing list
> Tech@lists.lopsa.org
> https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
> This list provided by the League of Professional System Administrators
>  http://lopsa.org/
>
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to