***: Nat_RH has joined #arpnetworks ant: up_the_irons: thanks for the insight
btw..."signon: Fri Oct 18 14:41:59 2013" <- that's how long freenode has been stable for me (i'm connected to calvino via ipv6) ***: CaZe has quit IRC (Read error: Connection reset by peer)
CaZe` has joined #arpnetworks
CaZe` is now known as CaZe plett: I'm on leguin.freenode.net via IPv6 and whois says "signon: Thu Nov 7 12:17:15 2013" up_the_irons: how do you find the signon timestamp? ant: i did /whois ant ant plett: I just did /whois plett CaZe: I wonder what's wrong with mine. plett: 09:24 [freenode] -!- idle : 0 days 0 hours 6 mins 41 secs [signon: Thu Nov 7 12:17:15 2013] ant: oh..right the second ant wasn't necessary up_the_irons: signon at: Wed, 11 Dec 2013 23:16:45
lol my node sucks
"holmes" SpaceDum1: Since you ask about your self you only have to specify the nickname once.
Twice for asking about another user and their server.. mercutio: is it any word as the second word?
cos i've always used servername before? SpaceDum1: Otherwise it will just give you the information about the client that the server you are connected too have. ***: SpaceDum1 is now known as SpaceDump mercutio: doing /whois spacedump and /whois spacedump spacedump returns the same info for me
and it tells your idle time but not signon time SpaceDump: Hm. :]
Perhaps some sort of feature in your client that always asks using the nick twice then.
Only the server holding the client knows about the idle time. ***: LT has joined #arpnetworks hazardous: signon timestamp
shows for anyone on your server
if ytou're both on leguin or wolfe or whatever
if you want a timestamp for another server, need to repeat the name SpaceDump: Excactly.
That information is only held by the server that the user is connected to. CaZe: Great, now that you have that figured out, you can fix my problem. :D hazardous: happy holidays everyone SpaceDump: CaZe: Choose a better server? :p CaZe: I've been on asimov, calvino, morgan, wolfe, hobana, and leguin.
Within the past 24 hours. SpaceDump: I've never felt that this network was stable... :p m0unds: haha ***: Rope has joined #arpnetworks SpaceDump: I'm mostly on ircnet. Very stable. :] ***: RandalSchwartz has joined #arpnetworks
RandalSchwartz has quit IRC (Changing host)
RandalSchwartz has joined #arpnetworks
LT has quit IRC (Quit: Leaving)
easymac has quit IRC (Read error: Connection reset by peer)
easymac has joined #arpnetworks
CaZe has quit IRC (Read error: Connection reset by peer)
CaZe` has joined #arpnetworks
CaZe` is now known as CaZe
CaZe has quit IRC (Remote host closed the connection)
CaZe` has joined #arpnetworks
CaZe` is now known as CaZe
CaZe has quit IRC (Read error: Connection reset by peer)
CaZe` has joined #arpnetworks
CaZe` is now known as CaZe
CaZe has quit IRC (Remote host closed the connection)
CaZe` has joined #arpnetworks
CaZe` is now known as CaZe
CaZe has quit IRC (Read error: Connection reset by peer)
CaZe` has joined #arpnetworks
CaZe` is now known as CaZe mercutio: i dunn owhy freenode is so unstable
isn't it meant to be for programmers and open source projects and linux and so on
if it was some warez network or something i'd understand
i assume it must be due to ddos attacks, but i dunno who would wnat to ddos freenode brycec: IRC networks are an easy target. For nubs cutting their teeth on such attacks, a big, well-known network is prime. m0unds: well, it's not /just/ ddos or targeted attacks that cause instability
lots of different varying quality hardware, networks, etc mercutio: maybe too many servers m0unds: yeah, probably plays a role too
i don't particularly like freenode CaZe: But it appears that I'm the only one with the problem. m0unds: womp womp mercutio: it's only the instabliity that bothers me
and only slightly
my client auto reconnects m0unds: i disable /part /quit or disco msgs in every channel i'm in
so i just never see people leave
hahaha mercutio: haha
for some reason on arp channel i see disconnects all the time CaZe: I do too. mercutio: like ap age of them
i think it just means people need to talk more m0unds: yeah, haha mercutio: like this channel has no-one talking for 12 hours sometimes i think m0unds: oh, i guess i suppress join msgs too
only way i can tell CaZe is having issues is this : 14:45 -!- CaZe` is now known as CaZe
hahaha mercutio: oh caze is high on the list of reconnects heh CaZe: What's my quit reason, btw? mercutio: 09:52:57 <-- ? CaZe (~caze@2607:f2f8:a678::2) has quit (Remote host closed the connection) _ ant
09:53:11 --> ? CaZe` (~caze@2607:f2f8:a678::2) has joined #arpnetworks
that was from like 25 hours ago CaZe: Is it ping out? mercutio: a whole lot of crap like that CaZe: Hmm. m0unds: which client do you use CaZe? CaZe: irssi mercutio: the _ant is just cos he's in the online list btw m0unds: hm
i'm using irssi too, but i'm not having any issues mercutio: i think it's cos he's using ipv6 m0unds: i am too mercutio: oh m0unds: haha, yeah
that's why it's weird mercutio: openbsd used to have ethernet timeouts m0unds: you're on the same version of irssi as me mercutio: maybe it's something like that m0unds: yeah, maybe CaZe: Yeah, it's fine when I switch over to ipv4. mercutio: oh CaZe: Oh, wait. mercutio: what OS are you using caze? CaZe: lag_max_before_disconnect = 30sec
Maybe I should set that higher. m0unds: hm CaZe: OpenBSD mercutio: shouldn't need to
30 seconds is ages
what version of openbsd? m0unds: lag_max_before_disconnect = 5min CaZe: SOme old snapshot. m0unds: mine's default
5min is ridiculously high mercutio: do you get the e1000g0 timeouts?
or em0
or whatever it is lteo: i sometimes wonder if ipv6 privacy addresses will cause irssi to drop mercutio: e1000g0 is what solaris calls it heh CaZe: OpenBSD 5.3-current (GENERIC) #181: Sat Jun 8 11:55:10 MDT 2013 mercutio: hmm i'm using something aqround there too CaZe: No, I disabled mpbios. mercutio: wow
I'm on Jun 3
self compiled kernel lteo: mercutio: are you talking about these timeouts? "em0: watchdog timeout -- resetting" mercutio: i sohuld update sometime
lteo: yeh
sounds aboutr right
i don't have any in my dmesg to compare to though CaZe: Yes, that's the old mpbios problem. lteo: i still get those timeouts even on recent snapshots mercutio: lteo: weird
i think i did something or other
to fix it
maybe i adjusted timeouts in em driver
god knows :)
i remember it annoyed me before CaZe: Heh.
User Kernel Config
UKC> disable mpbios 53 mpbios0 disabled
I have that in my dmesg.
That should be three lines though. lteo: i disabled mpbios as well, otherwise openbsd won't even boot ;) avj: yeah, i also still have to disable mpbios to even get my openbsd vm to boot here mercutio: i can't see anything obvious
if_em.h:#define EM_TX_TIMEOUT 1 /* set to 5 seconds */
i wonder if that's default
i lowered timeout of transmit lteo: default is:
#define EM_TX_TIMEOUT 5 /* set to 5 seconds */ mercutio: not raised it
hmm
maybe i was hoping it'd trigger easier if it was broken still lteo: as far as i can tell though, the watchdog timeout timestamps don't coincide with the times my irssi drops mercutio: i also lowered EM_MAX_TXD
hmm CaZe: I was talking with sthen@ awhile back. mercutio: someone should look into why those timesouts happen properly. CaZe: A different interrupt table is used depending on if mpbios is enabled or not. mercutio: it used to hapepn to me heaps CaZe: Let me grep my logs. mercutio: 11:16AM up 192 days, 22:41, 1 user, load averages: 0.14, 0.18, 0.16
i haven't had it once
and logs fit in dmesg CaZe: 02/16/11 13:04:12 <toddf> it tracks back to the bios itself providing a bogus mpbios table with a single cpu mercutio: clock: unknown CMOS layout
is my last message CaZe: 02/16/11 13:04:24 <toddf> if that were fixed, 'disable mpbios' would be a thing of the past in kvm
02/16/11 13:04:42 <toddf> now for bonus points, arpnetworks is interested in a newer bios without this restriction, and infact there exists such an animal
02/16/11 13:05:02 <toddf> problem however is that newer biosen don't have the 'hit f12 for booting off a cdrom' which arpnetworks considers crutial for customers mercutio: you don't need disable mpbios on the new node CaZe: 01/13/12 17:36:03 <sthen> there are different interrupt tables depending on whether mpbios is used
Well, it's not really a big deal. mercutio: i've had so many cut and paste problems with linux recently
grr
i swear i've had cut and paste issues for over 10 years
and it's still not fixed :/ mike-burns: It's getting worse.
There's no respect for primary & secondary buffers anymore. toddf: whats even worse than that
is stooopid webkit
pwsafe has a nice little feature
put something into the clipboard, once it's pasted once, remove it
webkit reads the clipboard 3 times trying to figure out which encoding it should use for a pasted event mike-burns: Hah. Of course it does.
Kids these days. toddf: because nobody ever thought you could read data off the clipboard, then parse it three different ways, you have to call methods which directly read the clipboard in three different ways mike-burns: I find browsers to be the biggest UI offenders.
Most people full-screen their browser and consider it their desktop environment, which means that those of us who don't just aren't cared for. m0unds: i don't know many people who use full screen browsers, tbh ant: i don't know many who don't... mike-burns: Designers measure browsers using terms like "screen size", not "window size". toddf: when you can emulate a pc in a web browser I think we've reached the point of diminishing returns in native apps avj: the constant fullscreen browser seems to be a windows thing m0unds: and smart designers make efficient use of available space mike-burns: Definitely a Windows thing, but I've been seeing it more and more on OS X. lteo: i think it started with os x lion mike-burns: The Epiphany browser starts maximized by default.
The Xombrero browser is targeting us, but it hasn't seen any commits for a month. brycec: I usually maximize my browser... But that's because A) My monitors are relatively small. B) It's the only thing I need to focus on... or I put a console on my second (3rd, 4th, etc) monitor
Also, using a tiling WM lends itself well to full-screen everything m0unds: the only hting i regularly run in fullscreen is the incident tracker i use at work, and that's only because the ui doesn't scale at all toddf: typically I'm interacting with the browser as a reference for what I'm working on or copying data to/from the browser for interacting with a remote site. this pretty much means I'll be having some terms to look at with my browser, kindof requiring the browser not to be full screen lest the terms and the browser play footsy on who is gonna get the z order mike-burns: Yeah I do what toddf does. The browser is a very unimportant and tiny part of my computing life. CaZe: I have click to raise, and mouse gets focus. staticsafe: i always have a browser open and am constantly using it, I also have Putty open all the time CaZe: Pretty handy for situations like that. mike-burns: That's another thing Kids These Days don't appreciate enough: alternative window focus/raise strategies. m0unds: staticsafe: same here staticsafe: i suppose I can be classified under the Kids These Days category mike-burns: When I was your age I wrote my XF86Conf by hand, and I liked it! m0unds: haha CaZe: I remember going to the computer lab to print out the Linux XFree86 HOWTO. staticsafe: what is XF86Conf? m0unds: haha CaZe: It was somethign like 80 pages. staticsafe: The configuration file XF86Config of the XFree86 project is used by the X server to set necessary configuration parameters.
oic
yea its not necessary anymore CaZe: Back in the day, when the chances of X just working at a decent resolution after an install were pretty slim.
Like, you'd be lucky to get 640x480. mike-burns: I was always worried about my monitor catching fire. The HOWTO warned me about it! CaZe: Or emitting x-rays. staticsafe: CRTs :D m0unds: wee brycec: lol
email, tickets, and reference stuff are a very large part of my job, hence the browser open fullscreen 24/7. The other "half" of my job is sysadmin and code, so I always have at least one terminal open on every workspace toddf: some of us don't use the browser to access our notes on how to do things nor do we use a browser for email brycec: I know. I'm just explaining my usage scenario and reason(s) for using it fullscreen m0unds: ... toddf: I played with the chromebook a little bit in the store once. It certainly caters to your use case. suggesting you're not the only one ;-( brycec: lol plett: For me, it depends on the size of the monitor
Here on my laptop, I run a browser full screen
At work, where I have a 30" monitor, it's only ever half or a third of the screen
In both cases the browser window is somewhere approximately a thousand pixels wide
And yes, tiling window manager in both places mike-burns: Looks like my browser is 847px wide. toddf: xombrero -> default_zoom_level=0.65 -> 640pxx480px ***: Rope is now known as LeprechuanEse mercutio: this channel is off-topic so much :) m0unds: haha, there's a topic?
get stuff set up and it just kinda hums along, moreso than any provider i've used ***: LeprechuanEse has quit IRC (Ping timeout: 245 seconds) m0unds: whoa mercutio: yeh i haven't really had many problems m0unds: only issue i've had was nlayer's fault for being lame ***: jbourne has joined #arpnetworks jbourne: Hello to room! staticsafe: hi jbourne: Hello staticsafe :) m0unds: exciting night jbourne: indeed ***: jbourne has left "Leaving" CaZe: Over six hours, and no disconnect.
I've seen my lag go over 30s a few times. m0unds: cool, so raising that seems to have stabilized it? CaZe: Yell, it just tolerates a larger lag. ***: CaZe has quit IRC (Remote host closed the connection)
CaZe` has joined #arpnetworks
CaZe` is now known as CaZe CaZe: Spoke too soon. ***: brachiation has quit IRC (Ping timeout: 246 seconds) brycec: lol up_the_irons: nothing wrong with off topic. what else would we talk about? ;) mnathani: its not like our services are not rock solid that we have people complaining about outages
(That was meant as a compliment) ***: mnathani has left "WeeChat 0.4.2" up_the_irons: :) ***: mnathani has joined #arpnetworks up_the_irons: mnathani : appreciated :) -: up_the_irons wanders off ***: mnathani has quit IRC (Quit: WeeChat 0.4.2)
mnathani has joined #arpnetworks
mnathani has quit IRC (Client Quit)
mnathani has joined #arpnetworks
mnathani has quit IRC (Client Quit)