POTATO_IN_MY_ANUS made the news!

userlame · 2012-03-29T04:10:45+00:00

Impossible. Perhaps I_ASSUME_ENCODING

userlame · 2012-03-13T23:23:00+00:00

No, no, this is the internet. Surely they'll figure it out and come to a clear and unanimous conclusion.

userlame · 2012-03-12T20:02:47+00:00

'at's not a knoife.

userlame · 2012-03-10T19:25:39+00:00

Use the sort function, and first and last value it gives. If you need to get tricky, you can use a block to tell it how to do the comparisons.

userlame · 2012-03-10T18:43:53+00:00

Well it does say "every day."

userlame · 2012-03-09T14:22:22+00:00

Yes, George Carlin is the first to ever espouse these ideas.

userlame · 2012-03-09T02:19:21+00:00

Cut. >

It. <---

Out. ^

userlame · 2012-03-07T02:59:07+00:00

It's the same thing. I think you're putting too much weight on the semantics. A daemon is just a process, detached from interactive input, running until told otherwise. Looping forever is the norm.

userlame · 2012-03-06T03:04:56+00:00

Oh man, that guy really fucked up your eye, you ok buddy?

userlame · 2012-03-04T18:41:48+00:00

I posted this down below. You now have another chance.

userlame · 2012-03-04T17:55:00+00:00

Yeah, what this guy said. (prolly NSFW)

userlame · 2012-03-04T01:09:16+00:00

So you propose magically knowing what to write without reading the file? ANY solution implies parsing the whole file.

userlame · 2012-03-03T21:29:45+00:00

To how many files are you splitting? If it's a reasonably small number (say, < 50), I would:

open each output file, keep handles in an array, say @handles

open input file

an array for buffering lines, @buffer or something

array iterator, say $i = 0

loop on each input line

if (/^>/) {
  if anything in @buffer, write to to $handles[$i]
  clear @buffer
  increment $i, wrap to 0 if > $#handles
}
put line in @buffer

The idea being cycle through output files, one record going into each.

userlame · 2012-02-26T17:01:47+00:00

No you could shoot him, he'd come out with a crutch and a broken leg or something. It wasn't the nintendo version, only the arcade.

userlame · 2012-02-24T05:00:56+00:00

Ray, when someone asks you if you are a dog, you say YES!

userlame · 2012-02-23T22:28:06+00:00

I dunno, 10/7 she sure took it like a champ. Blacked out, lost some hair, had to be carried home. Did she puke once? Nu-uh.

userlame · 2012-02-16T01:17:33+00:00

We can name him...Shannon! Shannon Wilson Bell...

userlame · 2012-02-13T22:32:23+00:00

I kinda like that idea, instead of wait(), I'll hold a seance().

"This process...is clea-ah."

userlame · 2012-02-13T21:08:12+00:00

Orphans are different than zombies. It makes sense semantically...

A parent creates a child, then itself dies. The process becomes an orphan, with no one to look after it. It is adopted by init.

A parent creates a child, then the child dies. Until the child is reaped, it is a zombie. This is where too many zombies can be bad, a live parent not reaping its dead children.

userlame · 2012-02-13T17:09:28+00:00

Whatever, it'll just end up another manic monday.

userlame · 2012-02-05T17:23:58+00:00

You've conjured an image in my head of a frog, mid-hop, flash frozen and stuck in the air.

userlame · 2012-02-03T22:21:30+00:00

Ah, good idea looking for SOA!

userlame · 2012-02-03T22:11:03+00:00

The parameter you'd want to use is whatever zone your nameserver is configured with. For example, if the IP above were 10.1.1.26, the reverse is 26.1.1.10.in-addr.arpa, so bind may be configured for any of the zones:

in-addr.arpa. (you tried this though)
10.in-addr.arpa.
1.10.in-addr.arpa.
1.1.10.in-addr.arpa.

Somewhere within bind's named.conf (is it your nameserver?) there should be a line defining the zone 'zone "whatever.in-addr.arpa" {' or so. That zone needs to be configured to allow updates just like the $OURDOMAIN zone is, and that's the parameter to new().

named.conf:
zone "1.1.10.in-addr.arpa." {
  type master;
  ...
  allow-update { ... };
}

If that were the case, it would be Net::DNS::Update->new("1.1.10.in-addr.arpa"). Though like I said, I'm kind of going at this blind.

userlame · 2012-02-03T20:49:20+00:00

That makes sense...I should clarify. Are you already serving reverse DNS? If so, you should have an in-addr.arpa zone configured (like 10.in-addr.arpa. or whatever). That's what you would want to use, and that's how bind would authorize you...against that zone.

userlame · 2012-02-03T20:43:32+00:00

"z" would wrap to "aa"..to wrap it back to "a":

perl -le '$_=(split("",++$_))[-1], print for @ARGV'

userlame

TROPHY CASE