From mike at oakleyweb.com Tue Jul 6 17:17:28 2004 From: mike at oakleyweb.com (Michael Wood) Date: Mon Aug 2 21:33:55 2004 Subject: [Oc-pm] hello Message-ID: <00ec01c463a7$062c95d0$cb2b14ac@guavasmobile> Greetings, Things have been particularly nasty lately...I've been inundated with deadines, fires and all manner of unpleasant ilk. I will not be able to attend, but please if you all wish by all means don't let me stop you from going on to meet tonight. Things are going to be getting worse - I really need someone to step up to the plate and bat for OCPM - I have the keys and the title - just one driver is all it'll take... I'm really sorry... -Mike From dgwilson at sonomasystems.net Tue Jul 6 17:24:28 2004 From: dgwilson at sonomasystems.net (Wilson, Douglas) Date: Mon Aug 2 21:33:55 2004 Subject: [Oc-pm] hello Message-ID: <8FFBCE8C59BF814B8258905C9B4D8317100D88@sonoma-main.sonoma.local> The day after a holiday (unless you got Friday off) is maybe not a great time for a meeting (nor is the first day of the month like last month :), nevertheless, I'll be there this time. If anyone else happens to show, then I'll see you there :) Maybe we should switch to "the first tuesday after the first wednesday" of the month similar to london.pm, so that the date doesn't sneak up on you as much? > -----Original Message----- > From: Michael Wood [mailto:mike@oakleyweb.com] > Sent: Tuesday, July 06, 2004 3:17 PM > To: oc-pm@pm.org > Subject: [Oc-pm] hello > > > Greetings, > > Things have been particularly nasty lately...I've been inundated with > deadines, fires and all manner of unpleasant ilk. > > I will not be able to attend, but please if you all wish by > all means don't > let me stop you from going on to meet tonight. > > Things are going to be getting worse - I really need someone > to step up to > the plate and bat for OCPM - I have the keys and the title - > just one driver > is all it'll take... > > I'm really sorry... > > -Mike > > _______________________________________________ > Oc-pm mailing list > Oc-pm@pm.org > http://www.pm.org/mailman/listinfo/oc-pm > From Brian.Cooke at VerizonWireless.com Tue Jul 6 17:39:53 2004 From: Brian.Cooke at VerizonWireless.com (Brian.Cooke@VerizonWireless.com) Date: Mon Aug 2 21:33:55 2004 Subject: [Oc-pm] hello Message-ID: <200407062239.i66MdwbU013059@www.pm.org> I second that idea. The day does sort of seem to come out of nowhere each month, especially these last two. I have a giant project that landed on me this morning, and it's 50/50 for me making it tonight. If these last couple of queries will just hurry up... :-O If it all wraps up by 6:30 or so then I'll make an appearance. -----Original Message----- From: oc-pm-bounces@pm.org [mailto:oc-pm-bounces@pm.org]On Behalf Of Wilson, Douglas Sent: Tuesday, July 06, 2004 3:24 PM To: oc-pm@pm.org Subject: RE: [Oc-pm] hello The day after a holiday (unless you got Friday off) is maybe not a great time for a meeting (nor is the first day of the month like last month :), nevertheless, I'll be there this time. If anyone else happens to show, then I'll see you there :) Maybe we should switch to "the first tuesday after the first wednesday" of the month similar to london.pm, so that the date doesn't sneak up on you as much? > -----Original Message----- > From: Michael Wood [mailto:mike@oakleyweb.com] > Sent: Tuesday, July 06, 2004 3:17 PM > To: oc-pm@pm.org > Subject: [Oc-pm] hello > > > Greetings, > > Things have been particularly nasty lately...I've been inundated with > deadines, fires and all manner of unpleasant ilk. > > I will not be able to attend, but please if you all wish by > all means don't > let me stop you from going on to meet tonight. > > Things are going to be getting worse - I really need someone > to step up to > the plate and bat for OCPM - I have the keys and the title - > just one driver > is all it'll take... > > I'm really sorry... > > -Mike > > _______________________________________________ > Oc-pm mailing list > Oc-pm@pm.org > http://www.pm.org/mailman/listinfo/oc-pm > _______________________________________________ Oc-pm mailing list Oc-pm@pm.org http://www.pm.org/mailman/listinfo/oc-pm From mike at oakleyweb.com Tue Jul 6 18:34:01 2004 From: mike at oakleyweb.com (Michael Wood) Date: Mon Aug 2 21:33:55 2004 Subject: [Oc-pm] hello References: <8FFBCE8C59BF814B8258905C9B4D8317100D89@sonoma-main.sonoma.local> Message-ID: <010101c463b1$b79d7f50$cb2b14ac@guavasmobile> I have the keys to ocpm's website and the mailing list. Taking care of them and heading up meetings/planning presentations is pretty much it... ...I'll hand it all over if you're up to the task ;) -Mike ----- Original Message ----- From: "Wilson, Douglas" To: "'Michael Wood'" Sent: Tuesday, July 06, 2004 3:25 PM Subject: RE: [Oc-pm] hello > > Let me know what is required...I'll give it a go > > > -----Original Message----- > > From: Michael Wood [mailto:mike@oakleyweb.com] > > Sent: Tuesday, July 06, 2004 3:17 PM > > To: oc-pm@pm.org > > Subject: [Oc-pm] hello > > > > > > Greetings, > > > > Things have been particularly nasty lately...I've been inundated with > > deadines, fires and all manner of unpleasant ilk. > > > > I will not be able to attend, but please if you all wish by > > all means don't > > let me stop you from going on to meet tonight. > > > > Things are going to be getting worse - I really need someone > > to step up to > > the plate and bat for OCPM - I have the keys and the title - > > just one driver > > is all it'll take... > > > > I'm really sorry... > > > > -Mike > > > > _______________________________________________ > > Oc-pm mailing list > > Oc-pm@pm.org > > http://www.pm.org/mailman/listinfo/oc-pm > > > From bill at daze.net Wed Jul 7 01:16:36 2004 From: bill at daze.net (bill@daze.net) Date: Mon Aug 2 21:33:55 2004 Subject: [Oc-pm] FBI @ Oakley Message-ID: <20040706231329.R65164@droid.daze.net> Hoping the subject will get your attention. :) Just thought I'd pass this along. It's not specifically perl, but it could provide useful security information to consider while developing... and it's at Oakley. ---------- Forwarded message ---------- Date: Mon, 5 Jul 2004 12:29:34 -0700 (PDT) From: Hershel Remer Reply-To: UUASC@UUASC.org To: uuasc-announce@UUASC.org Subject: UUASC-OC July 2004 Program UUASC-OC Unix Users Association of Southern California Orange County Chapter July Meeting --------------------------------------------- FBI Security --------------------------------------------- Monday, July 12, 7-9 PM Oakley, Inc. One Icon, Foothill Ranch --------------------------------------------- NOTE: Due to circumstances beyond our control, the Firewall Demo originally scheduled for July is postponed until 2005. However, we are fortunate to provide something special this month, as the FBI is sending one of its top agents with 26 years in the Bureau to come speak to us about computer security. At the July meeting of UUASC-OC, Special Agent Jon Lipsky will focus on UNIX systems, but aspects of computer security which are relevant for other operating systems will also be discussed. And, he will also describe the National Criminal Intelligence Sharing Plan. As always, there will be a generous opportunity for audience questions. For this special presentation, the UUASC invites everyone with an interest in computer security. Computer security impacts all computer users. The opportunity to hear the views of the FBI should be of interest to nearly everyone using a computer. Special Agent Lipsky serves as the Acting Director of the Los Angeles Joint Drug Intelligence Group, a national multi-agency task force specializing in criminal intelligence, information sharing, money laundering and financial investigations involving client requested products and services. He has experience in completing time-sensitive, discreet and complex criminal, civil, and administrative investigations; managing computer systems and data analysis; intelligence, link analysis protocol and risk management. CARPOOL INFO: If you are interested in joining a carpool with other members, please post an email to the general list, uuasc@uuasc.org , requesting carpool info. DINNER AFTER THE SHOW: Possible. FOR DIRECTIONS PLEASE VISIT OUR WEBSITE: http://uuasc.org/oc.html , where you will find a detailed map. --------------------------------------------------------------------- The UUASC is for all persons using Unix either personally or professionally, or interested in learning more about Unix. We recognize all varieties of Unix, including (without prejudice) HP/UX, Linux, SVr4, Solaris, AIX, and BSD. This is a good place to meet others with similar interests and broaden your skills and knowledge. Generally, meetings include a technical presentation on a hardware or software topic of current interest to the Unix community and a round-table discussion of current topics of interest to the group. We are always looking for interesting presentations and your suggestions are most welcome. Please join us this month and bring along your friends or co-workers. Also, please forward this announcement to others who may be interested and feel free to post it to wherever you wish, both electronically and physically. If you receive more than one announcement by email, please let us know so we can keep our lists current. ------------------------------------------------------------------------ This list is for announcements only. Send all discussion to the regular UUASC list. For details, send message "info UUASC" to Majordomo@UUASC.org. To unsubscribe, send "unsubscribe UUASC-announce" to Majordomo@UUASC.org. From wyatt at draggoo.com Fri Jul 9 12:09:24 2004 From: wyatt at draggoo.com (Wyatt Draggoo) Date: Mon Aug 2 21:33:56 2004 Subject: [Oc-pm] Chain of subs... Message-ID: <20040709100925.23427.h012.c001.wm@mail.draggoo.com.criticalpath.net> I'm writing a log parser for some things at work, and am trying to figure out the best way to run each line of the log through a chain of subroutines. Is an array of sub references the best way to go for this? Thanks, Wyatt Sample, untested code here: my @parsers = ( \&parser1, \&parser2, \&parser3, \&parser4 ) while (<>) { foreach my $parseSub (@parsers) { &$parseSub($_); } } sub parser1 { # do stuff... } ... -- Wyatt Draggoo From dgwilson at sonomasystems.net Fri Jul 9 12:32:30 2004 From: dgwilson at sonomasystems.net (Wilson, Douglas) Date: Mon Aug 2 21:33:56 2004 Subject: [Oc-pm] Chain of subs... Message-ID: <8FFBCE8C59BF814B8258905C9B4D8317100D94@sonoma-main.sonoma.local> > -----Original Message----- > From: Wyatt Draggoo [mailto:wyatt@draggoo.com] > Sent: Friday, July 09, 2004 10:09 AM > To: oc-pm@pm.org > Subject: [Oc-pm] Chain of subs... > > > I'm writing a log parser for some things at work, and am > trying to figure > out the best way to run each line of the log through a chain > of subroutines. > > Is an array of sub references the best way to go for this? That seems as good a way to go as any. Then you can easily add or remove any of the parsing actions. But if you are doing some of the same things in each subroutine (e.g. parsing the line into tokens), then you might think about doing some of the work before passing off the rest of the work to the subs. From wyatt at draggoo.com Fri Jul 9 12:49:20 2004 From: wyatt at draggoo.com (Wyatt Draggoo) Date: Mon Aug 2 21:33:56 2004 Subject: [Oc-pm] Chain of subs... Message-ID: <20040709104920.25429.h011.c001.wm@mail.draggoo.com.criticalpath.net> > > I'm writing a log parser for some things at work, and am > > trying to figure > > out the best way to run each line of the log through a chain > > of subroutines. > > > > Is an array of sub references the best way to go for this? > > That seems as good a way to go as any. Then you can easily > add or remove any of the parsing actions. But if you > are doing some of the same things in each subroutine (e.g. > parsing the line into tokens), then you might think about > doing some of the work before passing off the rest of the > work to the subs. Oops, I meant to put that into my initial e-mail. I'm parsing out the lines into a hash table first, and then I'll pass a reference to the hash table to each of the functions. Wyatt -- Wyatt Draggoo From dgwilson at sonomasystems.net Fri Jul 9 13:16:48 2004 From: dgwilson at sonomasystems.net (Wilson, Douglas) Date: Mon Aug 2 21:33:56 2004 Subject: [Oc-pm] Chain of subs... Message-ID: <8FFBCE8C59BF814B8258905C9B4D8317100D95@sonoma-main.sonoma.local> > > > I'm writing a log parser for some things at work, and am > > > trying to figure > > > out the best way to run each line of the log through a chain > > > of subroutines. > > > > > > Is an array of sub references the best way to go for this? > > > > That seems as good a way to go as any. Then you can easily > > add or remove any of the parsing actions. But if you > > are doing some of the same things in each subroutine (e.g. > > parsing the line into tokens), then you might think about > > doing some of the work before passing off the rest of the > > work to the subs. > > Oops, I meant to put that into my initial e-mail. > > I'm parsing out the lines into a hash table first, and then > I'll pass a > reference to the hash table to each of the functions. I'm all for keeping it simple, but if you wanted to, you could go OO and write a dispatching class something like: package MyLogDispatcher; sub new { my $class = shift; bless [@_], $class } sub process { my $self = shift; # tokenize @_ to %args or whatever $_->process(%args) for @$self; } package MyLogProcessor1; sub process { my $self = shift; # process (@_) } package MyLogProcessor2; sub process { my $self = shift; # process (@_) } package main; my $processor = MyLogDispatcher->new(qw( MyLogProcessor1 MyLogProcessor2 )); while (<>) { $processor->process($_); }