| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Comments:
<0> eggzeck, hey! i huh ?
<1> omg
<2> merlyn: lilo runs scripts that auto-k:line people ;)
<3> norton-protected fools
<4> Wow, merlyn made them all go
<5> people with bad software.
<0> eggzeck, sorry, ignore.
<6> my $out = shift || select; ... except that select is returning a string!?
<7> What's the distance between the North and South poles, BTW?
<8> lollernetgear
<9> merlyn: People get klined for that here.
<6> Which of course makes Perl real cranky.
<0> merlyn really does magic
<9> merlyn: It isn't considered good behavior.
<6> Why would select return a string?
<1> LAWLS. you run inferior AV software! HELLO!
<8> gumbybrain DCC SEND
<10> At least i think maybe manager want to make my pages aren't known to spamhaus as a hashref as each letter so you can send is a bug i discovered one day i discovered perl and brushing up skills in general don't return 0.
<1> (www.freeav.com)
<8> :O
<1> ohhhhhhhhh
<2> bingo.
<11> infi, the comments on that article are quite interesting as well
<12> there he goes
<9> Oh well.
<7> Uh-oh.
<13> Cctoide: if you wish to ***ume the earth is a perfect sphere, it would be half the distance around the equator
<14> hate XML::Simple.
<8> So much for merlyn, huh
<0> can someone explain to me why that worked ?
<2> Nei: Grasping for anything that defends your position still does not render the points in the article fallacious.
<12> r3nd3r: bug in netgear firmware for one of their routers
<0> pravus, bug in the router ??? u kidding! ?
<0> i thought i'd be something with the irc client
<14> and a bug in Norton/Symantec (there were two exploits in that line)
<12> nah, most clients are fairly resistant to DCC attacks these days
<13> Cctoide: however, I make it roughly 19,955.8656 km
<9> It is supposed to protect the client.
<12> i remember when mIRC had a bug that would allow you to connect someone to the chargen port >]
<7> NeoThermic: *nod*
<4> I can't believe merlyn did that, I'm actually laughing here.
<5> WTF?
<1> zomg merlyn
<2> merlyn: newb!
<15> merlyn: don't do this again please :-)
<2> heh
<1> merlyn: they k-line for that :)
<16> merlyn: for future reference, don't exploit DoS bugs
<9> merlyn: It is considered a DoS and gets a kline.
<1> merlyn: that was too f'in funny.
<5> who is the "they" that killed me on the first attempt?
<16> Me.
<5> that's pretty unfair judgement.
<9> merlyn: YOU disconnected them first.
<5> I hadn't seen that in a month and a half.
<16> I see many of those a day.
<5> I didn't think anyone was still running broken software.
<12> merlyn: and now you know why
<16> we get rid of the "unfriendlies" that do that
<5> Well - anyway, call me shocked that people have trigger fingers here.
<4> That was quite entertaining actually
<5> I'm not a random dude.
<4> Thank for the laugh guys.
<13> Cctoide: does one have an answer yet? :)
<5> and YOU of all people know that.
<9> merlyn: But you ARE.
<16> you look like a random dude to me.
<5> a simple "please don't do that" would have done
<9> merlyn: You are a freenode user.
<12> i don't know it's that suprising
<5> And where in the login information does it say "don't do that?"
<1> merlyn, random dude. tootin along on the internet :)
<12> it's considered abuse and freenode has a policy to take care of it
<9> merlyn: Actually, I did warn you, but apparently the tolerance level has gone down.
<5> please point at the web page that says that this particular behavior isbanned.
<5> and I would have appreciated *that*
<5> it's not like I would have repeated it.
<12> merlyn: how is j-random-freenode staff supposed to know that?
<9> merlyn: I can't believe you are arguing this. You are not banned, and it ended up being no worse than what you inflicted.
<5> Anyway... people need to play their power games, oh well.
<16> Like I said, I see many a day. I'm not going to randomly ***ume that your client's user info is accurate and not kline you based on it.
<5> LoRez - I'm not entirely convinced that you can't believe my ident'ed persona
<5> is the security really lax here?
<16> your ident info doesn't say anything but what e-mail address you have.
<5> I see <i=merlyn@blue.stonehenge.com>
<5> yes - and if you hang out in #perl, you know that's not an unfamous address.
<16> I've been here for years.
<5> right
<5> so you know ME.
<16> no.
<17> Haha
<5> eh?
<17> Perl Felon
<16> Md had to point out who he thought you were.
<16> and he unklined you.
<4> Maybe someone hijacked his system
<5> anyway - a simple "hey, we ban people for that" would have been enough.
<4> :P
<5> especially given that I'm not new to the block either.
<5> your power has been demonstrated, but it's still a bit of an overkill.
<16> I'll try and keep track of all 456 random people in #perl just for you from now on :)
<9> merlyn: I did say that to you, but if freenode staff bans EVERYONE for doing that, why shouldn't they ban you? I am not getting that.
<16> I don't expect that "reputable" people would do stuff like that.
<5> heh - perhaps you haven't seen http://www.lightlink.com/fors/
<12> you might expect reputable people to be punished more severly
<5> I get myself into crap occasionally
<16> consider it an occasion, go have a drink or something ;)
<5> I don't expect people to NOT FIX THEIR ****ING SOFTWARE after 90 days of this mistake.
<18> heh
<5> so that's why I was shocked.
<5> I expected it to do nothing.
<4> Do you know how dumb people can be?
<4> I mean, even tech support guys
<4> ;p
<2> s/even/especially/
<0> hey!
<19> internet explorer still has 13+ wide open security holes, and yet 80+% of the intarweb uses IE.
<5> so I'll go back to my original question... anyone had experience with testing cooperating kids from Test::More?
<0> i was in tech support
<2> r3nd3r: and I hope you fled.
<0> :(
<0> well yeah i did
<5> I'm just running in circles trying to figure out how to do this.
<0> :P
<4> Yeah, damn, I can't even talk with one professionally.
<2> r3nd3r: you're the guy I got connected to at Dell who would try and have me reboot production servers for failed SCSI drives (where the indicator light said FAILED), aren't you?
<4> hahaha
<0> oh-oh
<20> anyone here familier with DBD::ODBC?
<20> DBD::ODBC::st fetchrow_hashref failed: [Microsoft][ODBC SQL Server Driver]String data, right truncation (SQL-01004)(DBD: st_fetch/SQLFetch (long truncated DBI attribute LongTruncOk not set and/or LongReadLen too small) err=-1) at RuscompDB.pl line 84.
<20> ?
<2> huhlig: that appears to be an MSSQL-specific error message.
<20> hmm
<0> infi, no.. but ironically our call center did take calls for dell
<2> huhlig: msdn.microsoft.com or whatever.
<1> r3nd3r: i am so sorry to hear that.
<0> infi, i was with earthlink =O
<12> huhlig: iirc you have to set LongReadLen in the DBI options... i may have an example here... let me look
<2> r3nd3r: yep, and that contract was why we switched 55 servers to HP :b
<20> ok
<0> synth, thank you.
<21> huhlig: there are flags/attributes to be set for when the data length is too large.
<2> r3nd3r: not your fault, though ;) just your scripted troubleshooting wasn't very effective :)
<20> tybalt89, any idea what I should be looking for?
<12> huhlig: i think you do something like: $dbh->{LongReadLen} = <some large number>;
<20> ok
<0> infi, actually we never handled server related problems
<0> infi, did u ask where the call center was located ?
<2> nah
<21> huhlig: LongReadLen flag/attribute
<0> infi, it mustve been the atlanta one
Return to
#perl
or
Go to some related
logs:
#debian
#web
#bash
debian stop xserver
libdvdcss2-amd64
3com pcmcia gentoo yenta
#php
#linux
+fedora 4 live cd
#awk
|
|