Sixth Annual Triangle InfoSeCon Conference - "Call for Papers"

Sixth Annual Triangle InfoSeCon Conference - "Call for Papers"
>
> Members and Fellow ITSec Professionals,
>
> CALL for PAPERS is now open! See conference webpages
> (http://raleigh.issa.org/conference.html).
>
> Spread the word within your organizations and among your cohort.
>
> The Raleigh ISSA Chapter announces the sixth annual Triangle InfoSeCon. This
> Information Security conference is on Thursday, October 21, 2010, at the
> McKimmon Center in Raleigh, North
> Carolina located on the campus of

Problem: Sufficiently long regular expressions start to look like line noise and become unmaintainable

Solution: Use perl regular expressions with the /x modifier

perlre manpage reads:

/x
Extend your pattern's legibility by permitting whitespace and comments.
These are usually written as ``the /x modifier''...

The /x modifier itself needs a little more explanation. It tells the
regular expression parser to ignore whitespace that is neither
backslashed nor within a character class. You can use this to break up
your regular expression into (slightly) more readable parts.

The # character is also treated as a metacharacter introducing a

LOPSA-NJ has started a mailing list for the people that run technical user groups (LUGs,sysadmin user groups, SAGE or LOPSA chapters, and so on). The purpose of this mailing list is to encourage information sharing on topics such as:

How to promote your group, how to find speakers, how to get started, tips on how to run a meeting, volunteer retention, and anything else related to the running of such groups. The only forbidden topic is who's computer/editor/OS/language/whatever is better/worse that mine/yours.

To be on this list you must be the chair/co-chair/president/board-member or somehow be in charge of organizing a user group with live, in-person meetings (or be involved in starting one).

Recently I was building a ZenPack for Zenoss. The ZenPack included an Event Command which executed a custom script. I wanted to store the custom script in the ZenPack and I didn’t want to do anything other than have proper script dependencies in place for it to work. (Read More)

I need to transfer about 40TB from one zfs box to another box because of a problem of initial setup in box 1 that left it without redundant raid and it now has a failing disk. ZFS points this out quite nicely, but we have to get all that data off before the disk fails completely, even though it's a backup box. (Apparently you can't replace a disk in a pure stripe without zfs having conniptions).

So, what to do? zfs send/recv are a marvelous tool for this, especially combined with a pure network stream like ttcp or netcat or the like. First, start up 20 listening processes on the receiver listening on 20 different ports piped into zfs recv. Second, make a snapshot on all of the filesystems so you have a consistent starting point. zfs snapshot -r zpool1@mig1. Third, send all of these filesystems over in parallel using a quick bash script and incrementing the port number.