[2011-07-31 18:00:36 CEST] No hub address configured. Use '/connect
' to do so. [2011-07-31 18:00:51 CEST] Connecting to dc.blicky.net:2780... [2011-07-31 18:00:51 CEST] Connected to 188.142.33.141:2780. [2011-07-31 18:00:51 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-07-31 18:00:51 CEST] Welcome to the ncdc development hub! [2011-07-31 18:00:51 CEST] [2011-07-31 18:00:51 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-07-31 18:00:51 CEST] [2011-07-31 18:00:51 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-07-31 18:00:51 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-07-31 18:00:51 CEST] [2011-07-31 18:00:51 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-07-31 18:00:51 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-07-31 18:00:51 CEST] [2011-07-31 18:00:51 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-07-31 18:00:51 CEST] [2011-07-31 18:00:51 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-07-31 18:00:51 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-07-31 18:00:51 CEST] [2011-07-31 18:01:38 CEST] hi everyone [2011-07-31 18:01:43 CEST] #ncdc.nick = xmw [2011-07-31 18:01:43 CEST] Your new nick will be used for new hub connections. [2011-07-31 18:01:51 CEST] Disconnected. [2011-07-31 18:01:56 CEST] Connecting to dc.blicky.net:2780... [2011-07-31 18:01:56 CEST] Connected to 188.142.33.141:2780. [2011-07-31 18:01:56 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-07-31 18:01:56 CEST] Welcome to the ncdc development hub! [2011-07-31 18:01:56 CEST] [2011-07-31 18:01:56 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-07-31 18:01:56 CEST] [2011-07-31 18:01:56 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-07-31 18:01:56 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-07-31 18:01:56 CEST] [2011-07-31 18:01:56 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-07-31 18:01:56 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-07-31 18:01:56 CEST] [2011-07-31 18:01:56 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-07-31 18:01:56 CEST] [2011-07-31 18:01:56 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-07-31 18:01:56 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-07-31 18:01:56 CEST] [2011-07-31 18:02:18 CEST] nick? [2011-07-31 18:02:23 CEST] better [2011-07-31 18:02:30 CEST] hi [2011-07-31 18:02:31 CEST] heh, and there I wondered how you managed to compile from the git repo but hadn't found /set nick yet :) [2011-07-31 18:03:51 CEST] lazyness i guess :) [2011-07-31 18:04:10 CEST] this i my first dc session ever. i'm just a packager so far. [2011-07-31 18:04:49 CEST] woah, trying DC for the first time? seriously? [2011-07-31 18:04:55 CEST] that's really encouraging :) [2011-07-31 18:06:04 CEST] i had others downloading stuff in the pat. [2011-07-31 18:06:18 CEST] s/pat/past/ [2011-07-31 18:08:16 CEST] i'm just testing the stability and feature set of ncdc to convince myself adding it to the gentoo main tree. [2011-07-31 18:08:34 CEST] (it's in the xmw overlay for now) [2011-07-31 18:09:03 CEST] woah [2011-07-31 18:09:03 CEST] +me [2011-07-31 18:17:25 CEST] Yorhel, what do you think about a file transfer logfile? [2011-07-31 18:17:43 CEST] on my todo list [2011-07-31 18:17:51 CEST] neat :) [2011-07-31 18:17:56 CEST] in addition to transfer stats etc [2011-07-31 18:18:08 CEST] oh it would be awesome [2011-07-31 18:18:16 CEST] per user stats? [2011-07-31 18:18:49 CEST] xmw: just curious; will you add the git ebuild to the main tree or are you planning on ebuilds for the tarballs? [2011-07-31 18:19:12 CEST] Blackheart: let's start with global stats :) [2011-07-31 18:22:38 CEST] Yorhel: the default policy is to prefer (snapshot) tarballs over live ebuilds (checksums, bug-tracking,...) but we can have both. [2011-07-31 18:23:55 CEST] Yorhel: it would be cool if you point out revisions ("releases" ) [2011-07-31 18:25:14 CEST] point out revisions? how? [2011-07-31 18:25:55 CEST] on the tarballs: be prepared to update them quite often. I tend to release often now that it's still beta, and don't really enjoy seeing old versions around [2011-07-31 18:26:23 CEST] sure. [2011-07-31 18:26:45 CEST] Yorhel: mind explaining fl_local.c:fl_refresh_process()? [2011-07-31 18:27:25 CEST] is there any process in some other part in the code that should prevent a missing [share] section? [2011-07-31 18:27:58 CEST] so let's just stick to a live git ebuild. [2011-07-31 18:28:20 CEST] the segfault i see on my mac is caused by that missing and g_key_file_get_keys returning NULL which g_strv_length doesn't like [2011-07-31 18:28:35 CEST] they weird thing is on my centos box this doesn't happen [2011-07-31 18:28:50 CEST] xmw i can give you a nudge if Yorhel releases ;) [2011-07-31 18:29:30 CEST] kaste: that assertion failure shouldn't trigger an abort(), so ncdc should stay running even when g_strv_length() is called with NULL [2011-07-31 18:29:37 CEST] kaste: agreed on that [2011-07-31 18:30:01 CEST] well it segfaults [2011-07-31 18:30:49 CEST] segfaults, even? hmm, do older glib versions lack the assertion? [2011-07-31 18:30:56 CEST] either way, it is a bug [2011-07-31 18:31:50 CEST] I believe changing that to something simple as "names ? g_strv_length(names) : 0" would work [2011-07-31 18:32:11 CEST] you mean new, i am building against 2.28 [2011-07-31 18:32:21 CEST] yes that should work [2011-07-31 18:33:09 CEST] but let me check whether the rest of the code handles a len=0 correctly [2011-07-31 18:33:34 CEST] you shouldn't be in that branch [2011-07-31 18:33:38 CEST] it should, but I added the "force refresh even without [share]" later on [2011-07-31 18:34:22 CEST] (highlighting in the chat would be a neat gmmick) i'm off to some recreational activities. have fun [2011-07-31 18:34:46 CEST] xmw: chat colours are definitely on my todo list :) [2011-07-31 18:35:05 CEST] how long is that list? :) [2011-07-31 18:35:06 CEST] shades of gray are colors, too. [2011-07-31 18:35:09 CEST] kaste: huge [2011-07-31 18:35:33 CEST] kaste: how should I not be in that branch? [2011-07-31 18:36:04 CEST] kaste: change of plans, bouldern, now. cya [2011-07-31 18:37:46 CEST] the comment reads: refresh share, which consists of multiple dirs, which only mathematician would consider 0 dirs to be :) [2011-07-31 18:38:12 CEST] heh [2011-07-31 18:38:52 CEST] it should work for 0 dirs as well [2011-07-31 18:39:20 CEST] only have to see whether g_strfreev() accepts NULL or not [2011-07-31 18:39:33 CEST] doesn't did a 5 line test before i asked [2011-07-31 18:39:58 CEST] k, then that needs a special-case as well [2011-07-31 18:40:11 CEST] glib is rather inconsistent there, g_free() does accept NULL [2011-07-31 18:40:24 CEST] (which I love to make use of) [2011-07-31 18:42:10 CEST] oh wait it does [2011-07-31 18:42:14 CEST] sorry [2011-07-31 23:27:03 CEST] ping [2011-07-31 23:27:09 CEST] Unknown command 'ping'. [2011-07-31 23:27:12 CEST] unping [2011-08-01 00:32:50 CEST] Yorhel: have you thought about shares per server? [2011-08-01 08:10:15 CEST] kaste: yes, but it is impossible to implement that in a secure way on NMDC [2011-08-01 08:13:04 CEST] doesn't mean I won't do it (if I have the time), but not without some huge warning messages [2011-08-01 08:44:05 CEST] where's the Problem? [2011-08-01 08:44:16 CEST] ah nevermind i get it [2011-08-01 08:44:48 CEST] well at least the lis tyou send when someone browses you could be different without a problem right? [2011-08-01 08:45:35 CEST] yes, that's possible, but not too reliable [2011-08-01 08:45:44 CEST] but I guess it'd be reliable enough [2011-08-01 08:46:32 CEST] the problem with NMDC is that it's pretty much guessing from which hub an incoming client-client connection came [2011-08-01 08:47:03 CEST] a more reliable solution is to open a separate port for every hub you're connected to [2011-08-01 08:47:23 CEST] but that doesn't really improve security in the slightest [2011-08-01 08:51:51 CEST] there have been several posts about it on the DC++ blog, https://dcpp.wordpress.com/2008/07/22/multiple-shares-in-nmdc-revisited/ links them together nicely [2011-08-01 08:53:51 CEST] thanks for the read [2011-08-01 10:43:57 CEST] ok Yorhel i believe the bug is on your side [2011-08-01 10:44:39 CEST] the abort is triggered in the log routines which are called in the assertion and this only happens if G_DISABLE_CHECKS is not set [2011-08-01 10:45:13 CEST] so you rely on your glib being built with --enable-debug which at least mine isn't [2011-08-01 10:46:14 CEST] and as far as i can tell the doc doesn't specify g_strv_length to be aware of NULL pointers [2011-08-01 10:46:56 CEST] yes, if g_strv_length() doesn't want NULL then the bug is on my side regardless of what happens [2011-08-01 10:48:21 CEST] hmm, is G_DISABLE_CHECKS a compile-time define? [2011-08-01 10:48:33 CEST] well the docs are terse, it just doesn't say anyting about it [2011-08-01 10:48:37 CEST] yes [2011-08-01 10:48:53 CEST] http://developer.gnome.org/glib/stable/glib-running.html does have a runtime G_DEBUG=fatal_criticals which turns those assertions into fatal errors [2011-08-01 10:49:17 CEST] my glib was built with --disable-debug [2011-08-01 10:49:30 CEST] but yeah, if the checks are removed at compile-time then things will indeed go wrong [2011-08-01 11:45:10 CEST] Kudos to the stability, i'm test hashing my share and microdc2 and shakespeer both already would have crashed :) [2011-08-01 11:53:46 CEST] glad to hear that [2011-08-01 12:40:26 CEST] yay! [2011-08-01 12:40:45 CEST] hash checking of downloaded files seems to work [2011-08-01 12:41:56 CEST] too bad my download speeds drops to 3MB/s in valgrind, though [2011-08-01 12:42:51 CEST] how do you browse someone else or download? [2011-08-01 12:43:00 CEST] \/help isn't helpful [2011-08-01 12:43:38 CEST] /browse , or 'b' key in userlist [2011-08-01 12:43:58 CEST] and in the file list, 'd' key to download any file [2011-08-01 12:44:54 CEST] won't work on this hub, though [2011-08-01 12:50:43 CEST] ok thanks [2011-08-01 12:50:50 CEST] you may want to update the help information then [2011-08-01 12:51:29 CEST] I did a few days ago, just hadn't pushed the commit yet :) [2011-08-01 15:49:33 CEST] ** Blackheart is loving the realtime info on the connections screen using enter [2011-08-01 16:54:02 CEST] um Yorhel why is the active ip global but the port per server? [2011-08-01 16:54:11 CEST] does that really make sense? [2011-08-01 16:54:24 CEST] is the port really per server? [2011-08-01 16:54:49 CEST] when i set active_port i get This command can only be used on hub and message tabs. [2011-08-01 16:55:14 CEST] ah nevermind [2011-08-01 16:55:18 CEST] sorry forgot the slash [2011-08-01 16:55:27 CEST] heh [2011-08-01 16:55:34 CEST] would still be a boon if that would be a seting i can tweak for every server [2011-08-01 16:56:09 CEST] although i could have my cake and eat it if i start more than one instance [2011-08-01 16:56:57 CEST] yeah, I've been thinking about supporting per-hub connection settings [2011-08-01 16:57:14 CEST] should be do-able, but not really high priority for now [2011-08-01 16:58:04 CEST] well doens't matter really, you could make a settings dir ption for the binary though. I know about the env var but i would find a cli switch easier [2011-08-01 16:58:25 CEST] there is [2011-08-01 16:58:39 CEST] then excuse my ignorance [2011-08-01 17:02:41 CEST] ah i see, then i can have a different user, connections and share which is awesome [2011-08-01 17:59:43 CEST] how did you build it on debian? I get ./configure: line 4841: syntax error near unexpected token `DEPS,' on squeeze [2011-08-01 18:00:18 CEST] never seen that one [2011-08-01 18:00:23 CEST] did you use the shippped autotools? [2011-08-01 18:00:57 CEST] last version I tested on debian was the 0.4 tarball (configure script included), which compiled without issues [2011-08-01 18:01:31 CEST] i'll try that then [2011-08-01 18:03:05 CEST] just tried latest git version with shipped autoconf, no problems here [2011-08-01 18:03:31 CEST] that's what i figured [2011-08-01 18:05:55 CEST] pkg-config wasn't installed via apt-get install autotools-dev autoconf and that caused it [2011-08-01 18:48:04 CEST] if I am disturbing you ignore but i am somewhat hooked on ncdc :) [2011-08-01 18:48:26 CEST] in cc.c does cc_listen_start really make sense? [2011-08-01 18:48:54 CEST] i am irritated by line 1140 where you get the listening port from the adress back [2011-08-01 18:49:03 CEST] i really see the point for the random port [2011-08-01 18:49:25 CEST] is there a chance that the port can be different from the one we specified if it wasn't 0? [2011-08-01 18:49:41 CEST] because then that would break firewall rules and other oder stuff [2011-08-01 19:11:50 CEST] I don't any OS would do that [2011-08-01 19:12:36 CEST] but it's easier to just fetch the actual port from the socket in every case than to do it in a separate branch for the zero port [2011-08-01 19:14:03 CEST] and I'm all for code reviews :) [2011-08-01 19:27:02 CEST] ** Blackheart [playing] #36778/49333 2:11/8:13 (26%) 02 - Ed Harrison - Tin Soldiers, from the album 'Neotokyo [N/A Disc 01]' [2011-08-01 19:27:10 CEST] yay, tmux ftw :) [2011-08-01 19:29:42 CEST] tmux has a plugin for that? [2011-08-01 19:30:18 CEST] nope, but you can throw text to any of their running windows [2011-08-01 19:31:11 CEST] so i did a perl script to fetch and parse the current playing song from mpc then send it to tmux [2011-08-01 19:31:40 CEST] then i created a binding in tmux to launch the script [2011-08-01 19:33:06 CEST] i actually discovered tmux a few days ago and won't be going back to screen :) [2011-08-01 19:36:27 CEST] yeah i switched a couple of years ago, althouth i still sometimes use screen when nesting [2011-08-01 19:36:37 CEST] i'd consider that script a non feature though :p [2011-08-01 19:37:07 CEST] Yorhel: did you test the chatting with weird characters? [2011-08-01 19:37:11 CEST] like ä :) [2011-08-01 19:37:49 CEST] it will likely come out right as an umlaut because we all have the same client but in another hub i'm in this displays wrong [2011-08-01 19:38:58 CEST] and i can't download a file list for the life of me :( [2011-08-01 19:39:46 CEST] kaste: ncdc used UTF-8 internally for everything, and since ADC hubs force UTF-8 on the messages it will work fine [2011-08-01 19:40:02 CEST] for NMDC hubs it depends on whatever you set for hub_encoding [2011-08-01 19:40:15 CEST] err, just "encoding", it is [2011-08-01 19:41:35 CEST] s/used/uses/ [2011-08-01 19:42:41 CEST] oh i actually have to set the environment on this jail [2011-08-01 19:42:51 CEST] can't type accens or anything [2011-08-01 19:44:15 CEST] undefined locales ftw [2011-08-01 19:44:22 CEST] hmm doesn't the hub say anything about its encoding in the handshake? [2011-08-01 19:44:41 CEST] kaste: nope [2011-08-01 19:45:21 CEST] NMDC is like IRC in that aspect. except people on IRC tend to be clever enough to tell everyone to use UTF8 nowadays [2011-08-01 19:45:22 CEST] *lol* [2011-08-01 19:46:44 CEST] yep that's better thanks [2011-08-01 19:49:24 CEST] ááá äÄ ññññ [2011-08-01 19:49:26 CEST] ok [2011-08-01 19:49:33 CEST] ** Blackheart got fancy characters [2011-08-01 19:59:37 CEST] ßßß [2011-08-01 21:17:59 CEST] ok i give up i setup my own server and connected with two clients on the same host to the server and i can't download the file list [2011-08-01 21:18:06 CEST] what could i be doing wrong? [2011-08-01 21:18:57 CEST] since it's the same computer it really should rule out forwarding, fw and any other connection related stuff [2011-08-01 21:38:51 CEST] btw i con't think it's sensible to rule out 127.* as ip adresses in commands.c line 250 [2011-08-01 21:39:57 CEST] at least it makes testing on localhost hard [2011-08-01 21:43:14 CEST] localhost != 127/8 ;-)) [2011-08-01 21:51:49 CEST] kaste: use your own network IP, then :) [2011-08-01 21:52:46 CEST] but what's stderr.log saying? [2011-08-01 21:53:17 CEST] with log_debug enabled [2011-08-01 21:54:23 CEST] ok is it posible that direct messages don't work yet? [2011-08-01 21:54:36 CEST] i.e. private messaging? [2011-08-01 21:56:15 CEST] they work [2011-08-01 22:00:49 CEST] what's going wrong, exactly? [2011-08-01 22:03:56 CEST] i expected pm's to go through the hub which would have worked with both clients passive but it apparently doesn't [2011-08-01 22:04:13 CEST] i have two passive ncdc's in the same local hub and they can't send each other pm's [2011-08-01 22:04:25 CEST] i'll set one active and see if that's it [2011-08-01 22:04:37 CEST] pm's should go through the hub, indeed [2011-08-01 22:04:45 CEST] so either the hub is broken or ncdc is bugged [2011-08-01 22:05:02 CEST] again, check stderr.log :) [2011-08-01 22:05:15 CEST] such issues are easily debugged [2011-08-01 22:10:37 CEST] i connected with two other clients now and it won't work either, so i assume the hub is broken :/ [2011-08-01 22:12:45 CEST] oh, so pm's flow unencrypted through the hub? [2011-08-01 22:13:01 CEST] it doesn't use a client to client connection? [2011-08-01 22:13:19 CEST] Blackheart: indeed [2011-08-01 22:13:25 CEST] i have to definitelly take a look to the protocol specifications :) [2011-08-01 22:13:48 CEST] teamfair.info [2011-08-01 22:14:49 CEST] there's also a new NMDC documentation project: http://nmdc.svn.sourceforge.net/viewvc/nmdc/trunk/NMDC.txt?revision=1&view=markup [2011-08-01 22:15:44 CEST] great, thanks for the info [2011-08-01 22:16:17 CEST] and some recent discussion on more secure PMs, though I don't see this getting an implementation anytime soon... http://www.adcportal.com/forums/viewtopic.php?f=55&t=724 [2011-08-01 22:20:17 CEST] i never thought it worked this way, at least they should change the "feature" to non-private message! [2011-08-01 22:20:25 CEST] ** Blackheart shakes fist [2011-08-02 00:45:40 CEST] ok i hit another one, log's attached http://tehsuck.de/paste/index.php?show=1 [2011-08-02 00:46:12 CEST] i was trying to share something and wanted to autocomplete on the path [2011-08-02 00:46:27 CEST] i can't reproduce it atm though [2011-08-02 01:18:52 CEST] On that note i'd scrap a few lines in that region and either use http://developer.gnome.org/gio/2.28/GFilenameCompleter.html or try to make use of wordexp/glob [2011-08-02 01:20:41 CEST] that should end up being a lot more powerful than something homebrewed, i'll test tomorrow [2011-08-02 09:42:44 CEST] heh [2011-08-02 09:43:41 CEST] kaste: your valgrind output shows a problem with the autocompletion, indeed. but it crashed because of something entirely different [2011-08-02 09:43:54 CEST] which I just managed to reproduce :D [2011-08-02 09:44:39 CEST] open userlist -> go back to hub tab -> /disconnect -> go to userlist -> crash [2011-08-02 09:47:47 CEST] on the path_suggest(): I can't really explain how those errors happened, when I read the code and compare it with your log, that error really shouldn't happen [2011-08-02 09:49:15 CEST] a more high-level rewrite of that function probably makes sense [2011-08-02 09:52:08 CEST] i don't think that's what triggered it [2011-08-02 09:52:17 CEST] i haven't done that before [2011-08-02 09:53:14 CEST] your log suggests that the hub disconnected from network rather than from a /disconnect [2011-08-02 09:53:46 CEST] if you happened to have the userlist open at that time, then it would crash as well [2011-08-02 09:54:36 CEST] either way, the actual segfault happened in ui_userlist_sort_func() [2011-08-02 09:54:47 CEST] ahh that makes sense [2011-08-02 10:11:18 CEST] fix @ git [2011-08-02 10:12:57 CEST] let me also fix the g_strv_length() thing while I'm at it [2011-08-02 10:26:25 CEST] i already looked at those and fixed the obvious ones [2011-08-02 10:26:53 CEST] i am unsure about the ones in ui_util.c [2011-08-02 10:27:35 CEST] i also identified more functions where you are heading into trouble with glib [2011-08-02 10:27:52 CEST] ah [2011-08-02 10:28:20 CEST] the g_strv_length() in ui_util.c should be fine, c_sug shouldn't be NULL [2011-08-02 10:28:31 CEST] ok [2011-08-02 10:29:42 CEST] i did grep -I -o '\> glibcalls [2011-08-02 10:30:02 CEST] and then something that amounts to for l in $(cat glibcalls); do; if [[ -n $(grep -A 10 $l * |grep g_return_) ]]; then echo $l; fi; done; [2011-08-02 10:30:30 CEST] i have fiddled a bit with the constant 10 and the amount of results vary of course [2011-08-02 10:30:39 CEST] i think most are harmless [2011-08-02 10:31:30 CEST] but for example i noticed g_utf8_strlen which is definitely a candidate [2011-08-02 10:34:35 CEST] plus your use of the g_return macros is probably problematic in some places [2011-08-02 10:34:57 CEST] but it will take some time to properly look at those, since they are so many [2011-08-02 10:37:28 CEST] err, in human terms: you looked around all calls to g_ functions closely followed by a g_return_? [2011-08-02 10:39:44 CEST] yes [2011-08-02 10:39:56 CEST] i verified that g_ were only glib calls [2011-08-02 10:40:13 CEST] and then toook that list and did what you said in the glib tree [2011-08-02 10:41:22 CEST] aah, to get the assertions on the arguments of the glib functions [2011-08-02 10:41:32 CEST] yes [2011-08-02 10:42:18 CEST] the g_return macros are compiled to do {0/1} while(0); with debugging turned off [2011-08-02 10:42:27 CEST] they are essentially noops [2011-08-02 10:42:47 CEST] they shouldn't happen, anyway [2011-08-02 10:42:55 CEST] yes :) [2011-08-02 10:45:54 CEST] another thing are you hung up on ctrl e and u? [2011-08-02 10:46:21 CEST] because ctrl e would be jump to end of line and ctrl u clear line with readline [2011-08-02 10:47:34 CEST] not really, though my reasoning was http://g.blicky.net/ncdc.git/commit/?id=e95ac1c30129afd8dbab157947f8ec27589a793d [2011-08-02 10:48:33 CEST] ok, although i'd argue that people are more likely to come from a microdc2 background than dc++ [2011-08-02 10:49:28 CEST] i rather wonder about the fact if this operation is this common that it deserves a hot key [2011-08-02 10:49:37 CEST] i'd be totally ok with /refresh [2011-08-02 10:50:10 CEST] It's fairly common if you disable autorefresh [2011-08-02 10:50:31 CEST] you must have different usage habits :) [2011-08-02 10:50:36 CEST] and far more convenient than a command [2011-08-02 10:55:18 CEST] is the autorefresh so expensive that you don't enable it? [2011-08-02 10:56:00 CEST] nah, I just like having control over when a refresh happens [2011-08-02 10:56:26 CEST] I don't want ncdc refreshing my share when I'm moving files around, for example [2011-08-02 10:56:32 CEST] ok [2011-08-02 12:28:03 CEST] I think I'll do a 0.5 release today [2011-08-02 12:28:32 CEST] was planning to implement download destination changing in this release, but I guess that can wait [2011-08-02 12:47:39 CEST] you mean a "save as" equivalent? [2011-08-02 12:48:37 CEST] kaste: yeah [2011-08-02 12:49:06 CEST] ok that would be very low on my priority list :) [2011-08-02 12:49:52 CEST] heh, perhaps [2011-08-02 12:51:02 CEST] it is the kind of feature that you just expect to be there, but in the end probably not something often-used [2011-08-02 12:52:20 CEST] i don't really expect it from a console client [2011-08-02 12:52:34 CEST] i would expect it from a real gui [2011-08-02 12:54:12 CEST] you might want to avoid file name collisions [2011-08-02 12:54:46 CEST] xmw: is done automatically by adding a .$n extension [2011-08-02 12:57:27 CEST] linuxdc++ doesn't do that, which is a good source for frustration :( [2011-08-02 12:58:28 CEST] well, you loose filename based mimetype recognition and might end up with programms interpreting that as plit-parts by doing .$n *win* [2011-08-02 12:58:43 CEST] split-parts [2011-08-02 12:59:27 CEST] that's a lot better than having your files overwritten without a second thought :) [2011-08-02 13:00:08 CEST] just pop up the save-as dialog and leave it up to user choice [2011-08-02 13:00:25 CEST] please don't :) [2011-08-02 14:54:44 CEST] 0.5 online @ http://dev.yorhel.nl/download/ncdc-0.5.tar.gz [2011-08-02 19:25:53 CEST] still builds ;-) [2011-08-02 20:12:02 CEST] little dissapointin as distro maintainer [2011-08-02 22:47:23 CEST] Ok i see hashing errors for files with umlauts in them, is that something that can be helped? [2011-08-02 22:47:38 CEST] if the filename handling isn't right downloading them probably won't work either [2011-08-03 01:35:10 CEST] if i browse my share, share a new folder and it's done hashing - the browser window is not updated [2011-08-03 08:29:28 CEST] kaste: I even documented that in /help browse [2011-08-03 08:29:39 CEST] I'll fix that eventually, but it's going to be a pain [2011-08-03 08:31:34 CEST] and the hashing errors: hmm, I'm doing some magic with filename encoding while scanning the directories, in order to detect such problems early on, but I guess it's not working? [2011-08-03 09:04:19 CEST] i guess [2011-08-03 09:05:32 CEST] i know how complicated those encoding issues are. I guess it's ok to have that low on the priority list atm. If it annoys me, tell me what you need, i'll provide it [2011-08-03 09:05:53 CEST] s/annoys me/annoys you/ [2011-08-03 09:06:56 CEST] it annoys me to know nothing :P [2011-08-03 09:07:22 CEST] what's the encoding of the filename, and your system encoding? [2011-08-03 09:08:04 CEST] system encoding is utf-8 [2011-08-03 09:10:01 CEST] hmm now that i analyze it, it looks like an error here [2011-08-03 09:10:21 CEST] ls file | xxd makes it appear as if the umlaut is one byte [2011-08-03 09:10:27 CEST] that would be latin1 i guess [2011-08-03 09:10:38 CEST] however he managed to save it that way [2011-08-03 09:12:19 CEST] I don't suppose ls would do any re-encoding; does it display right in your terminal [2011-08-03 09:12:25 CEST] ? [2011-08-03 09:12:52 CEST] well if t would it should do so into the LANG setting, right? [2011-08-03 09:13:09 CEST] that would make most sense [2011-08-03 09:13:19 CEST] no it looks wrong, sorry for the stir [2011-08-03 09:13:34 CEST] since i have more files with funny chars, i guess it works [2011-08-03 10:36:04 CEST] hi [2011-08-03 10:36:44 CEST] how i can run ndc in background or as deamon [2011-08-03 10:40:47 CEST] using screen, dtach or tmux [2011-08-03 10:41:00 CEST] or any other alternative I am not aware of [2011-08-03 11:01:00 CEST] communication between client/server are secured? [2011-08-03 11:01:16 CEST] why you are not using any sort of encryption [2011-08-03 11:06:34 CEST] how i can encrypt my hub traffic? [2011-08-03 11:08:11 CEST] you'll have to use a TLS wrapper [2011-08-03 11:08:40 CEST] oh, new tarball up :) [2011-08-03 11:10:04 CEST] should i keep my profile, specially hashdata.dat? [2011-08-03 11:10:35 CEST] well, let's just try it anyways [2011-08-03 11:18:32 CEST] how i can use TLS wrappers any hint or link - will be appericated [2011-08-03 11:59:28 CEST] jahil: look into the faq http://dev.yorhel.nl/ncdc/faq [2011-08-03 12:00:40 CEST] i don't quite get the point though, the sensitive part would be c2c, or not? [2011-08-03 12:58:50 CEST] yes encryption between c2c (client2client) [2011-08-03 13:07:29 CEST] jahil: c2c encryption isn't supported yet [2011-08-03 13:08:12 CEST] and to my knowledge it is only available on ADC hubs anyway, which are in the minority [2011-08-03 14:27:48 CEST] kaste: just build some non-utf-8 locales, LANG=de_DE.ISO-8859-1 stat /pub/music/michael/Ärzte/Geräusch/Ärzte\ -\ Geräusch\ -\ 12\ -\ Richtig\ Schön\ Evil.mp3 | xxd [2011-08-03 14:29:23 CEST] to my knowledge, this filename is encoded as utf-8, and xxd reports 2 symbols for each umlaut [2011-08-03 14:31:03 CEST] (watch the changing quotation marks on en_US.UTF-8, de_DE.UTF-8, de_DE.ISO-5589-1 and smile) [2011-08-03 15:07:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-03 15:07:04 CEST] Connected to 188.142.33.141:2780. [2011-08-03 15:07:04 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-08-03 15:07:04 CEST] Welcome to the ncdc development hub! [2011-08-03 15:07:04 CEST] [2011-08-03 15:07:04 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-08-03 15:07:04 CEST] [2011-08-03 15:07:04 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-08-03 15:07:04 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-08-03 15:07:04 CEST] [2011-08-03 15:07:04 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-08-03 15:07:04 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-08-03 15:07:04 CEST] [2011-08-03 15:07:04 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-08-03 15:07:04 CEST] [2011-08-03 15:07:04 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-08-03 15:07:04 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-08-03 15:07:04 CEST] [2011-08-03 15:08:23 CEST] any chance to load the old chat log (backlog) into hub window at connect? [2011-08-03 15:08:49 CEST] [2011-08-03 15:08:49 CEST] Available commands: [2011-08-03 15:08:49 CEST] /browse - Download and browse someone's file list. [2011-08-03 15:08:49 CEST] /clear - Clear the display. [2011-08-03 15:08:49 CEST] /close - Close the current tab. [2011-08-03 15:08:49 CEST] /connect - Connect to a hub. [2011-08-03 15:08:49 CEST] /connections - Display the connection list. [2011-08-03 15:08:49 CEST] /disconnect - Disconnect from a hub. [2011-08-03 15:08:49 CEST] /gc - Perform some garbage collection. [2011-08-03 15:08:49 CEST] /grant - Grant someone a slot. [2011-08-03 15:08:49 CEST] /help - Request information on commands. [2011-08-03 15:08:49 CEST] /kick - Kick a user from the hub. [2011-08-03 15:08:49 CEST] /me - Chat in third person. [2011-08-03 15:08:49 CEST] /msg - Send a private message. [2011-08-03 15:08:49 CEST] /nick - Alias for `/set nick'. [2011-08-03 15:08:49 CEST] /open - Open a new hub tab. [2011-08-03 15:08:49 CEST] /password - Send your password to the hub. [2011-08-03 15:08:49 CEST] /pm - Alias for /msg [2011-08-03 15:08:49 CEST] /queue - Open the download queue. [2011-08-03 15:08:49 CEST] /quit - Quit ncdc. [2011-08-03 15:08:49 CEST] /reconnect - Shortcut for /disconnect and /connect [2011-08-03 15:08:49 CEST] /refresh - Refresh file list. [2011-08-03 15:08:49 CEST] /say - Send a chat message. [2011-08-03 15:08:49 CEST] /set - Get or set configuration variables. [2011-08-03 15:08:49 CEST] /share - Add a directory to your share. [2011-08-03 15:08:49 CEST] /unset - Unset a configuration variable. [2011-08-03 15:08:49 CEST] /unshare - Remove a directory from your share. [2011-08-03 15:08:49 CEST] /userlist - Open the user list. [2011-08-03 15:08:49 CEST] /version - Display version information. [2011-08-03 15:08:49 CEST] /whois - Locate a user in the user list. [2011-08-03 15:08:49 CEST] [2011-08-03 15:10:48 CEST] shouldn't be very hard [2011-08-03 18:55:23 CEST] what do you think about a search keybinding for the current buffer? [2011-08-03 18:59:30 CEST] ...and one for the userlist, and the file list [2011-08-03 18:59:48 CEST] the file list is especially in need of a search function [2011-08-03 19:01:57 CEST] what about the ability to filter a filelist via regexp? [2011-08-03 19:02:24 CEST] filter? wouldn't a normal search work? [2011-08-03 19:03:37 CEST] yeah, its actually the same [2011-08-03 19:11:58 CEST] what about an /alias command? i really found it quite useful while using weechat [2011-08-03 19:20:22 CEST] perhaps, not very high priority at this point, though [2011-08-04 10:18:00 CEST] hmm i'm not talented with strace, ncdc is using up a whole core, strace says it's trying to sendfile64 and i doubt it works [2011-08-04 10:18:21 CEST] how do i debug it? [2011-08-04 10:18:51 CEST] is there something like an upload queue that i could watch? [2011-08-04 10:20:21 CEST] or rather how do i find the cpu hog [2011-08-04 10:28:57 CEST] use the -c flag to get the stats summary [2011-08-04 10:29:20 CEST] the %time column should help [2011-08-04 10:40:20 CEST] kaste: connection list shows the active uploads [2011-08-04 10:40:45 CEST] also check stderr.log for possible sendfile() related errors [2011-08-04 10:42:34 CEST] although, if sendfile() hangs, then the UI is probably not responsive enough to open the connection list [2011-08-04 11:05:55 CEST] it's not hanging [2011-08-04 11:07:29 CEST] it's just running through and the return value is 0, which the man page suggests is successful but didn't do anything [2011-08-04 11:07:36 CEST] other than that it's polling [2011-08-04 11:07:57 CEST] which all seems rather normal but shouldn't take a whole core [2011-08-04 11:08:59 CEST] hmm indeed [2011-08-04 11:23:12 CEST] here's a sample if that helps http://tehsuck.de/paste/index.php?show=2 [2011-08-04 11:25:00 CEST] uhm, why is ncdc calling sendfile() with count=0? [2011-08-04 11:25:12 CEST] that sounds like the problem [2011-08-04 11:26:13 CEST] well otherwise a count of zero in the return would be an error right? [2011-08-04 11:26:40 CEST] I guess so [2011-08-04 11:29:23 CEST] still odd, handle_sendfile() should never be called with n->file_left = 0 [2011-08-04 11:36:15 CEST] ok i believe i found another unrelated oddity, when pm'ing with someone i got disconnected from the hub for MYINFO timeout (probably my weird network setup) [2011-08-04 11:36:49 CEST] the intersting thing is i reconnected and the pm opened up when the other guy said something plus a message that he connected appeared and another unrelated user also [2011-08-04 11:37:12 CEST] i believe this second appearance isn't expected behavour [2011-08-04 11:42:29 CEST] do you have the debug log for that? [2011-08-04 12:01:02 CEST] what nmdc command am i looking for? [2011-08-04 12:03:33 CEST] hmm ok the user that connected only appears once in the log in the middle of a string of myinfos [2011-08-04 12:03:42 CEST] there is nothing that singles him out in any way [2011-08-04 12:42:43 CEST] ok http://tehsuck.de/paste/index.php?show=3 [2011-08-04 12:43:06 CEST] this is a copy out of less which shows the unrepresentable chars as their equiv [2011-08-04 12:43:25 CEST] the user is MeisterKing and the char in that line is 0x09=tab [2011-08-04 12:43:45 CEST] don't know if it's related it's the only thing that seems a tad different [2011-08-04 12:48:07 CEST] that char shouldn't make a difference [2011-08-04 12:48:30 CEST] hub is going offline for a bit (30 min or so), need to removed a broken drive [2011-08-04 12:48:45 CEST] k [2011-08-04 12:48:58 CEST] Read error: Remote disconnected. [2011-08-04 12:48:58 CEST] Connection lost. Waiting 30 seconds before reconnecting. [2011-08-04 12:49:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:49:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:50:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:50:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:51:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:51:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:52:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:52:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:53:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:53:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:54:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:54:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:55:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:55:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:56:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:56:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:57:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:57:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:58:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:58:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 12:59:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 12:59:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:00:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:00:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:01:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:01:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:02:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:02:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:03:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:03:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:04:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:04:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:05:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:05:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:06:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:06:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:07:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:07:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:08:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:08:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:09:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:09:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:10:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:10:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:11:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:11:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:12:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:12:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:13:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:13:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:14:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:14:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:15:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:15:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:16:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:16:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:17:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:17:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:18:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:18:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:19:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:19:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:20:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:20:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:21:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:21:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:22:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:22:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:23:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:23:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:24:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:24:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:25:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:25:28 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:25:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:25:58 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:26:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:26:28 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:26:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:27:28 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:27:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:27:58 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:28:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:28:28 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:28:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:29:28 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:29:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:30:28 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:30:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:31:28 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:31:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:32:28 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:32:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:33:28 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:33:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:33:58 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:34:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:34:28 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:34:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:34:58 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:35:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:35:58 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-04 13:36:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:36:28 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:36:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:36:58 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:37:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:37:28 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:37:58 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:37:58 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-04 13:38:28 CEST] Connecting to dc.blicky.net:2780... [2011-08-04 13:38:28 CEST] Connected to 188.142.33.141:2780. [2011-08-04 13:38:28 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-08-04 13:38:28 CEST] Welcome to the ncdc development hub! [2011-08-04 13:38:28 CEST] [2011-08-04 13:38:28 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-08-04 13:38:28 CEST] [2011-08-04 13:38:28 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-08-04 13:38:28 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-08-04 13:38:28 CEST] [2011-08-04 13:38:28 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-08-04 13:38:28 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-08-04 13:38:28 CEST] [2011-08-04 13:38:28 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-08-04 13:38:28 CEST] [2011-08-04 13:38:28 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-08-04 13:38:28 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-08-04 13:38:28 CEST] [2011-08-04 13:44:13 CEST] *sigh* [2011-08-04 13:44:26 CEST] doing any maintenance on this box is pure hell [2011-08-04 14:10:09 CEST] why's that? [2011-08-04 14:23:00 CEST] would a shell on another box help you? [2011-08-04 14:54:54 CEST] that won't be necessary, I manage a few dedicated servers in my spare time [2011-08-04 14:55:33 CEST] this is just my fileserver @ home, which has a few annoyances [2011-08-04 14:55:54 CEST] all hardware should be able to support hot-swapping of hard-drives [2011-08-04 14:56:24 CEST] except the chassis, which requires me to unplug all HDDs, remove the motherboard, then remove the HDD and plug everything back :( [2011-08-04 14:57:51 CEST] and then in my lazyness I hadn't fixed the ordering of eth0 and eth1, so linux pretty much randomly assigns them and manages to do it wrong on every reboot [2011-08-04 14:59:59 CEST] ...and this was the 8th failed hard drive related to this fileserver since I bought it 3 years ago, lol [2011-08-04 15:03:48 CEST] impressive, that's quite the fail streak you got there [2011-08-04 15:04:42 CEST] sounds like you should have a look into the electric wiring or minimize the vibrations [2011-08-04 15:04:53 CEST] 8 is too many to be strictly random [2011-08-04 15:05:41 CEST] well, 1 of them was DOA and the other 6 were likely from a single batch [2011-08-04 15:06:11 CEST] ah ok, i usually try to avoid that [2011-08-04 15:06:25 CEST] and this looks like a regular failure [2011-08-04 15:06:34 CEST] I've learned to do that the hard way [2011-08-04 15:14:53 CEST] i think everyone has to :) [2011-08-04 15:31:28 CEST] you ppl need to move your fileservers to freebsd [2011-08-04 15:31:40 CEST] if you taste zfs you won't be back ;) [2011-08-04 15:31:57 CEST] I'm actually waiting for btrfs to mature [2011-08-04 15:32:35 CEST] sounds damn promising [2011-08-04 15:33:23 CEST] they are just promising to deliver the current zfs features to linux [2011-08-04 15:33:42 CEST] but yeah it awesome [2011-08-04 15:33:59 CEST] its like moving from svn to git [2011-08-04 15:35:55 CEST] heh, nice comparison [2011-08-04 15:39:08 CEST] isn't zfs available on linux? or is that not as stable as on BSD [2011-08-04 15:41:14 CEST] the problem is with the kernel license, as zfs should run in it [2011-08-04 15:41:32 CEST] actually you can barelly use zfs with fuse [2011-08-04 15:41:45 CEST] but you shouldn't even try it ;) [2011-08-04 16:43:20 CEST] oh man [2011-08-04 16:43:33 CEST] I lost count of how many times I make this same stupid mistake [2011-08-04 16:43:48 CEST] if(!u) { ...; u->something; ... } [2011-08-04 16:53:53 CEST] hehe at least you get an instant segfault [2011-08-04 17:12:36 CEST] kaste: in case you're still debugging/tinkering with the PM thing, I just changed how ui_msg_* works; check the git repo [2011-08-04 17:13:19 CEST] that will likely also affect your problem, hopefully in a positive way [2011-08-04 17:15:42 CEST] i wouldn't know how to [2011-08-04 17:15:59 CEST] it seems like rather random circumstances that i wouldn't know how to reproduce [2011-08-04 17:35:54 CEST] xmw: the ebuilds for the tarball releases don't really need to depend on makeheaders; generated header files are included in those [2011-08-04 20:01:49 CEST] My current idea for a file searching interface: http://p.blicky.net/5uz3h [2011-08-04 20:02:11 CEST] that's pretty much a direct mapping of the NMDC file searching capabilities to a command [2011-08-04 20:02:41 CEST] ADC allows for more advanced searches, but I guess that can be added later [2011-08-04 20:19:19 CEST] looks good [2011-08-04 20:48:44 CEST] I don't understand why they didn't just implement RE's [2011-08-04 20:48:55 CEST] adc is a little more powerful but not that much really [2011-08-04 20:49:27 CEST] that has been discussed in the past, actually [2011-08-04 20:49:45 CEST] shouldn't be too hard to fit within the framework of the interface you want to implement [2011-08-04 20:49:54 CEST] do you remember the reason they rejected it? [2011-08-04 20:49:54 CEST] was denied because they found it too DoS-heavy [2011-08-04 20:50:02 CEST] DoS? [2011-08-04 20:50:07 CEST] Denial of Service? [2011-08-04 20:50:08 CEST] http://dcpp.wordpress.com/2008/07/22/denial-of-service-id-like-one-please/ [2011-08-04 20:50:11 CEST] ya [2011-08-04 20:50:23 CEST] omg [2011-08-04 21:06:30 CEST] 5 exe Windows executables. [2011-08-04 21:06:33 CEST] yay! [2011-08-04 21:26:03 CEST] you realize that OS has a bit of a monopoly right :) [2011-08-04 21:33:58 CEST] yeah it should be replaed to "5 elf Elf Binaries" [2011-08-04 23:20:33 CEST] Yorhel: thanks for the hint on makeheaders [2011-08-04 23:21:42 CEST] Yorhel: you mentioned "i don't want to see old versions around", did you mean old releases or non-git builds? [2011-08-05 01:17:27 CEST] atlas fand ganymed: ping [2011-08-05 01:18:11 CEST] adding ~sparc ~ppc ~x86 keywords ;-) [2011-08-05 01:39:45 CEST] Yorhel: your release tarball behaves strange. configure.in line 20 complains about a missing makeheaders, but in fact, you test for absence of makeheaders and absence of $srcdir/src/main.h [2011-08-05 01:41:30 CEST] later on, the generated ./src/GNUmakefile complains about that in the auto_headers rule. [2011-08-05 01:45:52 CEST] this complain is invalid, because your configure already detected the presence of the header files (i.e. src/main.h) and the redundance of the header file re-creation (makeheaders call). [2011-08-05 01:48:08 CEST] so either you trust your own release tarball and the correctness of the shipped header files (dropping the dependency for makeheaders) or you just call makeheaders regardless of the presence of any (maybe corrupted) header files. [2011-08-05 01:50:53 CEST] but you will run into severe debugging headaches if systems show different errors depending on a makeheaders installation. [2011-08-05 02:08:31 CEST] Yorhel: maybe something like this http://dpaste.com/586643/ [2011-08-05 02:24:43 CEST] Yorhel: wrt network card names http://en.positon.org/post/Generate-persistent-udev-net-rules (i just realized that arch doesn't have these .rules by default.) [2011-08-05 02:26:52 CEST] you can choose a) random sorted card names upon reboot or b) incremented card names upon hardware change (rsync installs) [2011-08-05 07:17:59 CEST] xmw: on the versions: the releases are fine, I'm not expecting everyone to use the git version [2011-08-05 07:19:32 CEST] I'm already happy to see a package of a new version within a few days or so [2011-08-05 07:20:30 CEST] packages for the releases are rather less useful if it takes a week or more for them to get updated, with the current release cycle [2011-08-05 07:22:26 CEST] the reason why I still use makeheaders when it's available is to allow people to hack around in the code [2011-08-05 07:23:03 CEST] actually, the entire makefile rule shouldn't trigger when compiling from a tarball; the header files should be up-to-date and make should detect that [2011-08-05 07:23:21 CEST] which is why I put that warning there in case someone does manually edit a source file [2011-08-05 07:26:00 CEST] but now that I look at the 0.5 release, the mtimes of the header files aren't correct [2011-08-05 07:26:41 CEST] ** Yorhel makes a note to do a 'make clean' before 'make dist' next time [2011-08-05 07:30:36 CEST] and on the network card names: already checked archwiki and did one of the listed solutions :-) [2011-08-05 20:58:40 CEST] Let's all dance to the death of a clown [2011-08-06 13:20:26 CEST] nice [2011-08-06 13:20:31 CEST] file search is working pretty well [2011-08-06 13:21:43 CEST] when sorting of the results is implemented I might even prefer it to the search in GUI clients :D [2011-08-06 14:02:20 CEST] indeed, we're not in the posix bandwagon using curses just to be cool! :D [2011-08-06 14:17:54 CEST] wait, we aren't? [2011-08-06 14:17:56 CEST] damn [2011-08-06 14:18:23 CEST] it's still cool though, right? [2011-08-06 14:21:56 CEST] heh [2011-08-06 18:13:04 CEST] Yorhel, have you thought about being able to set a custom temp dir for the downloads? [2011-08-06 18:14:49 CEST] +me puts a higher disk quota on the ncdc jail [2011-08-06 19:23:00 CEST] yes, I did. I was even about to implement it [2011-08-06 19:23:16 CEST] until I realized that the existing files would have to be moved as well when changing the setting [2011-08-06 19:23:22 CEST] and then I got lazy :P [2011-08-06 19:30:29 CEST] you could probably also trick ncdc by turning ~/.ncdc/fl into a symlink [2011-08-06 19:37:21 CEST] well i was using a 2GB quota for the ncdc jail so i changed it to 8GB [2011-08-06 19:37:47 CEST] at the end i could even mount the homedir on the bulk storage pool [2011-08-07 10:30:22 CEST] exit [2011-08-07 15:14:41 CEST] Connecting to dc.blicky.net:2780... [2011-08-07 15:14:41 CEST] Connected to 188.142.33.141:2780. [2011-08-07 15:14:41 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-08-07 15:14:41 CEST] Welcome to the ncdc development hub! [2011-08-07 15:14:41 CEST] [2011-08-07 15:14:41 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-08-07 15:14:41 CEST] [2011-08-07 15:14:41 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-08-07 15:14:41 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-08-07 15:14:41 CEST] [2011-08-07 15:14:41 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-08-07 15:14:41 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-08-07 15:14:41 CEST] [2011-08-07 15:14:41 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-08-07 15:14:41 CEST] [2011-08-07 15:14:41 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-08-07 15:14:41 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-08-07 15:14:41 CEST] [2011-08-07 17:26:16 CEST] I like it when I code for several hours without testing, and it works on the first try [2011-08-07 18:24:03 CEST] Like a BOSS [2011-08-08 12:11:58 CEST] Upgrade warning: if you are sharing two files with the same name but different case in a single directory, ncdc will throw away all your hashdata and force a complete refresh [2011-08-08 12:12:10 CEST] on upgrade [2011-08-08 12:12:52 CEST] kaste: you will be affected by this, my git version now refuses to open your list because of this reason [2011-08-08 15:12:50 CEST] not that this is in any way surprising, but connecting to a hub with more than 10k users while running ncdc in valgrind does not really improve the responsiveness of the interface... [2011-08-08 15:14:00 CEST] ouch [2011-08-08 16:25:04 CEST] hmm, I guess it's time for a 0.6 release [2011-08-08 16:28:01 CEST] oh, perfect timing [2011-08-08 16:28:04 CEST] too lazy to test whether it compiles on debian & bsd, but I doubt I broke anything [2011-08-08 16:28:28 CEST] i'll compile it on FreeBSD Current ;) [2011-08-08 16:30:05 CEST] Blackheart: here's a current git snapshot, in case you'd like to try without getting the git deps: http://s.blicky.net/2011/ncdc-0.5g.tar.gz [2011-08-08 16:30:34 CEST] nice! [2011-08-08 16:30:38 CEST] *fetching [2011-08-08 16:37:52 CEST] nice [2011-08-08 16:39:56 CEST] compiles fine and has no obvious deficiencies on mac and centos [2011-08-08 16:40:06 CEST] trying debian and ubuntu [2011-08-08 16:40:12 CEST] what about adding a condition in the configure.in file to check the host is freebsd to update CPPFLAGS and LDFLAGS? [2011-08-08 16:40:32 CEST] kaste: nice [2011-08-08 16:41:11 CEST] Blackheart: to add the /usr/local dirs? really sounds more like a responsibility of the environment [2011-08-08 16:41:49 CEST] you said you're lazy the other day [2011-08-08 16:41:55 CEST] i guess i'm even more! [2011-08-08 16:43:26 CEST] kaste: have you got my earlier message on the file name thing? [2011-08-08 16:45:24 CEST] yeah [2011-08-08 16:46:18 CEST] does that mean it's the version that i am running now (yesterday or so) that exhibits the problem or the new one? [2011-08-08 16:46:18 CEST] k [2011-08-08 16:47:22 CEST] err, you'll lose your hash data when you upgrade, because of a bug in the earlier versions [2011-08-08 16:47:58 CEST] ouch [2011-08-08 16:47:59 CEST] hmm ok then what does the line file has been modified mean? [2011-08-08 16:48:32 CEST] ? [2011-08-08 16:49:05 CEST] you can avoid losing your hash data by renaming the offending files in your share [2011-08-08 16:49:07 CEST] gentoo seems ok btw [2011-08-08 16:49:15 CEST] no complains here [2011-08-08 16:49:15 CEST] like i know which ones :) [2011-08-08 16:49:21 CEST] should i rehash the whole thing? [2011-08-08 16:49:35 CEST] Blackheart: nah, your share is okay :) [2011-08-08 16:49:54 CEST] Error hashing "/dir/file": File has been modified. [2011-08-08 16:49:54 CEST] i disabled autorefresh btw [2011-08-08 16:50:15 CEST] it was kinda anooying to have an unresponsive client while chatting [2011-08-08 16:51:18 CEST] kaste: ah, that should only happen if the file was indeed modified in between the last refresh and before it finished hashing [2011-08-08 16:51:27 CEST] Blackheart: that's not a problem [2011-08-08 16:51:55 CEST] well it was in the middle of being uploaded i guess [2011-08-08 16:52:00 CEST] how do i fix this? [2011-08-08 16:52:21 CEST] kaste: just refresh, should fix itself [2011-08-08 16:53:18 CEST] also, I have found one case in your filelist on which the new version will complain [2011-08-08 16:53:24 CEST] it just causes the error to appear again [2011-08-08 16:53:53 CEST] ah well i'll just unshare it for now [2011-08-08 16:53:53 CEST] yay, /search :S [2011-08-08 16:55:30 CEST] sounds like a bug :( [2011-08-08 17:01:36 CEST] kaste: yeah, that was a bug. already have a fix [2011-08-08 17:03:10 CEST] :) [2011-08-08 17:03:49 CEST] For some reason software i touch breaks [2011-08-08 17:04:24 CEST] that's a good thing for developers :) [2011-08-08 17:04:50 CEST] i know, that's why i beta test software, makes no difference for me anyway :P [2011-08-08 17:08:44 CEST] so as ncdc now can search stuff we can conclude it's already the best DC client? ;) [2011-08-08 17:17:42 CEST] now with /search i really miss the possibility of creating aliases [2011-08-08 17:18:33 CEST] oh wait, i can actually create bindings on tmux [2011-08-08 17:23:45 CEST] ncdc is now better than microdc, at least, with the search feature it can do everything microdc could (but better ;) [2011-08-08 17:23:57 CEST] I'll come back on the /alias later, first dinner time [2011-08-08 17:33:39 CEST] enjoy your meal! [2011-08-08 17:35:10 CEST] bit early isn't it? [2011-08-08 17:36:42 CEST] well, here it's 17:35:59 already [2011-08-08 17:37:22 CEST] i believe we're all in the same timezone :0 [2011-08-08 17:37:36 CEST] our usage habits differ though [2011-08-08 17:54:20 CEST] heh, 17:30 is normal dinner time for me [2011-08-08 17:54:41 CEST] see i would consider doing that til after eight [2011-08-08 17:55:20 CEST] my stomach won't survive that [2011-08-08 17:57:28 CEST] ChangeLog lazyness: "Fixed various bugs" [2011-08-08 17:58:28 CEST] oh well, there's git log for those who want more details [2011-08-08 18:01:48 CEST] oh, linux 3.0.1 popped out on archlinux [2011-08-08 18:01:54 CEST] i thought it was a typo :D [2011-08-08 18:54:19 CEST] Guide updated with info about searching, browsing, download queue and the connections tab @ http://dev.yorhel.nl/ncdc/guide [2011-08-08 18:59:12 CEST] "My apologies for using such a generic search term as example. It just happens to be one that doesn't advocate piracy yet gives some results on most hubs" [2011-08-08 18:59:13 CEST] lol [2011-08-08 20:19:05 CEST] erm, i saw an cyan colored ! on my hub tab. I iterprete that as an highlight, but don't see an highlighted text in that window. [2011-08-08 20:20:01 CEST] cyan is just a "some chat happened" [2011-08-08 20:20:40 CEST] yellow is direct message or nick mentioned, but that's not highlighted in the log window yet... [2011-08-08 20:21:12 CEST] thanks. [2011-08-09 04:46:16 CEST] kaste: nudge fail, 0.6 was released http://git.overlays.gentoo.org/gitweb/?p=dev/xmw.git;a=commitdiff;h=1f47adc52695eefab91e7739d68bfd252ae0ec7d ;-) [2011-08-09 04:48:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 04:48:39 CEST] Connected to 188.142.33.141:2780. [2011-08-09 04:48:39 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-08-09 04:48:39 CEST] Welcome to the ncdc development hub! [2011-08-09 04:48:39 CEST] [2011-08-09 04:48:39 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-08-09 04:48:39 CEST] [2011-08-09 04:48:39 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-08-09 04:48:39 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-08-09 04:48:39 CEST] [2011-08-09 04:48:39 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-08-09 04:48:39 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-08-09 04:48:39 CEST] [2011-08-09 04:48:39 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-08-09 04:48:39 CEST] [2011-08-09 04:48:39 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-08-09 04:48:39 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-08-09 04:48:39 CEST] [2011-08-09 09:02:03 CEST] hehe not true xmw, told you about the release when you were leaving [2011-08-09 10:37:20 CEST] hmm, an option to load the last lines from a previous run in the log window would make something like a log compression feature rather hard to implement and inefficient on start-up [2011-08-09 10:38:03 CEST] so either I've got to scrap the log compression idea or use some different storage for the last few lines of a log window [2011-08-09 10:38:54 CEST] ...I guess I'll do the former [2011-08-09 10:42:45 CEST] are there hubs where this would be necessary in any sense? [2011-08-09 10:43:38 CEST] some people don't know how to stop talking [2011-08-09 10:44:27 CEST] well i often hang out in ##c and still the log's size is rather sane [2011-08-09 10:45:37 CEST] hmm, looks like I also need to figure out a way to properly serialize and parse formatting stuff when different lines can be formatted differently [2011-08-09 10:46:16 CEST] but that's probably do-able with some pattern matching [2011-08-09 10:46:49 CEST] what kind of formatting is there? [2011-08-09 10:47:10 CEST] system messages, join/quits and chat messages, mostly [2011-08-09 10:47:21 CEST] and why would that be serialized? Isn't the formatting done on the fly? [2011-08-09 10:47:54 CEST] yes, but I can't quite express colours in the log files :) [2011-08-09 10:48:18 CEST] Why would yiy save that? [2011-08-09 10:48:59 CEST] I don't, but you'd like to see colours when loading the last few lines of a log into the log window again, right? [2011-08-09 10:49:17 CEST] that's the same way weechat does it. It formats the messages whenever they come in, saves the naked text to the log and on reopening a channel you have been to the text appears without formatting [2011-08-09 10:49:27 CEST] not necessarily [2011-08-09 10:49:48 CEST] and even if you could reparse it just like you would if it came in couldn't you? [2011-08-09 10:51:05 CEST] hmm, depends on how I structure the logging of different messages, but if the differentiating and formatting happens in the display routines then yes [2011-08-09 10:51:29 CEST] which is where it belongs in my humble opinion [2011-08-09 10:52:29 CEST] still if it is too much trouble i'd just forget about it and display the last lines without formatting [2011-08-09 10:52:51 CEST] it may even be preferable since it shows you quickly that it's old [2011-08-09 10:53:01 CEST] and then there is another slight annoyance: chat messages can span multiple lines in the DC protocols, which could confuse the parse. But that's not very hard to work around luckily [2011-08-09 10:53:15 CEST] true [2011-08-09 10:54:16 CEST] if you don't mind i'd like for this feature to be turn-off-able, since i have one hub that automatically puts the last 20 lines htat where spoken into it's motd and this could become somewhat confusing [2011-08-09 10:54:33 CEST] of course [2011-08-09 10:55:01 CEST] though I planned to make it a global option rather than a per-hub one [2011-08-09 10:55:09 CEST] sure [2011-08-09 11:00:32 CEST] hmm i see big numbers in front of the buffers on the ncdc on mac [2011-08-09 11:01:34 CEST] not on arch though as it seems [2011-08-09 11:02:31 CEST] the numbers aren't random restarting ncdc produces the same numbers [2011-08-09 11:04:36 CEST] main has 0 when starting up, i open another server buffer then the number of main turns to 392 and the hub buffer claims 0; when switching to main then the hub buffer gets the number 588 and main gets 0 again [2011-08-09 11:04:44 CEST] does this right a bell? [2011-08-09 11:05:18 CEST] s/buffer/tab/? [2011-08-09 11:07:57 CEST] is that the correct lingo? :) yes i guess it's a tab [2011-08-09 11:09:45 CEST] doesn't ring a bell... in fact, sounds like a very odd issue [2011-08-09 11:09:56 CEST] do the alt+n keys work correctly? [2011-08-09 11:10:02 CEST] yes [2011-08-09 11:11:26 CEST] and the tabs are aligned correctly to take into account the extra characters needed for the longer numbers? [2011-08-09 11:11:30 CEST] yes [2011-08-09 11:12:26 CEST] ...lol [2011-08-09 11:12:41 CEST] really no idea how that can happen [2011-08-09 11:13:58 CEST] ok the numbers are less stable than i thought, opening another tab let's main keep 392 but pushes the first openend tab to 644 [2011-08-09 11:14:17 CEST] this is odd [2011-08-09 11:14:34 CEST] i mean even for the main buffer to get number 0 at the start is wrong [2011-08-09 11:15:47 CEST] it should be absolutely impossible when I look at the code [2011-08-09 11:16:25 CEST] so either compiler optimizations are screwing around or printw() isn't doing what I expect it to :-/ [2011-08-09 11:27:58 CEST] http://tehsuck.de/tmp/tabs.png [2011-08-09 13:00:36 CEST] hub going down again for 30min. or so. inserting replacement drive [2011-08-09 13:03:47 CEST] (after a cleanup process finishes) [2011-08-09 13:28:10 CEST] Yorhel: wrt logfiles, implement an detection iff the logfile was moved (monitor files device/inode id changes) and leave it up to the users. [2011-08-09 13:29:01 CEST] yeah, that's a better idea [2011-08-09 13:30:45 CEST] u can use logrotate/no-op/... [2011-08-09 13:36:16 CEST] brb, server maintenance [2011-08-09 13:36:26 CEST] Read error: Remote disconnected. [2011-08-09 13:36:26 CEST] Connection lost. Waiting 30 seconds before reconnecting. [2011-08-09 13:36:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:37:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:37:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:38:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:38:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:39:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:39:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:40:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:40:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:41:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:41:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:42:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:42:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:43:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:43:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:44:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:44:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:45:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:45:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:46:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:46:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:47:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:47:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:48:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:48:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:49:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:49:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:50:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:50:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:51:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:51:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:52:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:52:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:53:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:53:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:54:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:54:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:55:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:55:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:56:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:56:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:57:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:57:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:58:26 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-09 13:58:56 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:59:17 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-09 13:59:47 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 13:59:47 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-09 14:00:17 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 14:00:17 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-09 14:00:47 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 14:00:47 CEST] Could not connect to hub: Connection refused. Wating 30 seconds before retrying. [2011-08-09 14:01:17 CEST] Connecting to dc.blicky.net:2780... [2011-08-09 14:01:17 CEST] Connected to 188.142.33.141:2780. [2011-08-09 14:01:17 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-08-09 14:01:17 CEST] Welcome to the ncdc development hub! [2011-08-09 14:01:17 CEST] [2011-08-09 14:01:17 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-08-09 14:01:17 CEST] [2011-08-09 14:01:17 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-08-09 14:01:17 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-08-09 14:01:17 CEST] [2011-08-09 14:01:17 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-08-09 14:01:17 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-08-09 14:01:17 CEST] [2011-08-09 14:01:17 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-08-09 14:01:17 CEST] [2011-08-09 14:01:17 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-08-09 14:01:17 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-08-09 14:01:17 CEST] [2011-08-09 20:36:15 CEST] regarding the backlog thingie it could have his uses for PMs [2011-08-09 20:40:39 CEST] maybe there's not even need to save ansi colors at all and they could be shown as another color to make it different to the actual text [2011-08-09 20:41:18 CEST] regarding log compression... is nice to have a volume manager/filesystem with inline compression ;) [2011-08-10 12:14:56 CEST] lol [2011-08-10 12:15:16 CEST] don't ask incompetent hosting companies to install Arch for you [2011-08-10 12:15:33 CEST] http://p.blicky.net/lepj4 [2011-08-10 13:23:09 CEST] unbelievable, what company is that? [2011-08-10 13:24:36 CEST] hostd8.com [2011-08-10 13:24:53 CEST] but at least they managed to get it installed in a day :) [2011-08-10 13:25:22 CEST] I've had worse experience with another company, who needed a week and complained about how they had to hire a freelancer to do it [2011-08-10 13:26:16 CEST] ii believe they should change their line of business [2011-08-10 13:27:31 CEST] seem expensive for what they offer [2011-08-10 13:28:07 CEST] yeah, but they had some offer not displayed on their site [2011-08-10 13:28:29 CEST] this one -> http://www.webhostingtalk.com/showthread.php?t=1072025 [2011-08-10 13:34:11 CEST] still doesn't sound that great [2011-08-10 13:36:44 CEST] really? I've had a hard time finding dedicated server with both the RAM and the bandwidth [2011-08-10 13:38:15 CEST] why do you need that much ram? [2011-08-10 13:38:32 CEST] http://www.hetzner.de/hosting/produkte_rootserver/eq10 ? [2011-08-10 13:39:18 CEST] hetzner is expensive with more than 10TB/month bandwidth [2011-08-10 13:39:24 CEST] (from what I've checked) [2011-08-10 13:39:49 CEST] what else do you host, that you generate that much bandwidth? [2011-08-10 13:40:00 CEST] and the server will be used to server thumbnails - the more images that fit in RAM the better [2011-08-10 13:40:06 CEST] serve* [2011-08-10 13:40:32 CEST] a friend of mine has this magic ability that every site he creates is an instant success [2011-08-10 13:40:42 CEST] wow :) [2011-08-10 13:40:46 CEST] sample please [2011-08-10 13:41:27 CEST] this new server will be for zerochan.net [2011-08-10 13:42:02 CEST] ouch [2011-08-10 13:42:22 CEST] i get your problem :D [2011-08-10 13:46:35 CEST] hehe when he growse it to insane limits look into ovh :) [2011-08-10 13:46:50 CEST] they give you unlimited 10gbit ports but it costs [2011-08-10 13:47:09 CEST] hmm, I've had bad experiences with ovh [2011-08-10 13:47:13 CEST] oh really? [2011-08-10 13:47:22 CEST] i heard good things about them [2011-08-10 13:47:25 CEST] what was the problem? [2011-08-10 13:47:40 CEST] lots of US visitors had connection problems with them; but I've heard they're expanding in the US now so that may have been fixed now [2011-08-10 13:48:06 CEST] their customer site is google-translated from french [2011-08-10 13:48:50 CEST] and I've had two servers with them with 3 HDDs in total - all of them failed... [2011-08-10 13:49:07 CEST] ovh.com? i am looking at ovh.de and their german is good, haven't heard about the connectivity problems before [2011-08-10 13:49:37 CEST] they also have a .nl one, but both the English and Dutch translations were terrible [2011-08-10 13:49:55 CEST] well i see you are pushing the limits quite a bit [2011-08-10 13:51:50 CEST] how much traffic was your peak? [2011-08-10 13:52:13 CEST] I actually find it quite enjoyable to be able to play with such powerfull servers and actually have lots of traffic, simply as a past-time hobby :D [2011-08-10 13:52:37 CEST] our current thumbnail server only peaks around at 7MB/s or so [2011-08-10 13:52:38 CEST] an aquaintance used a few small hetzner boxes to proxy a big one which gave him a lot of trafic for cheap [2011-08-10 13:53:46 CEST] yeah, using multiple cheap servers tends to be cheaper than using a single powerful one [2011-08-10 13:53:52 CEST] that is 17 gig roundabout [2011-08-10 13:53:58 CEST] we're already distributing the load across 3 servers now [2011-08-10 13:55:12 CEST] i figured that for a big site like that [2011-08-10 13:55:25 CEST] gives you a nice point in your resume :) [2011-08-10 13:55:27 CEST] also, I've noticed that traffic tends to increase with 10-20% or so after a server upgrade, since everything responds faster [2011-08-10 13:55:41 CEST] heh, certainly :) [2011-08-10 14:06:05 CEST] are you cpu or io bound then? [2011-08-10 14:06:13 CEST] probably the latter then [2011-08-10 14:06:26 CEST] ever tried talking to your provider directly to see if they make you a special offer [2011-08-10 14:06:32 CEST] yeah, the static file servers are absolutely bored when it comes to CPU power [2011-08-10 14:07:04 CEST] special offers tend to be a lot more expensive than those cheap-ass stock servers :) [2011-08-10 14:07:20 CEST] (and I'm not paying for them anyway :P) [2011-08-10 14:11:55 CEST] do the banners pay for the bandwidth? [2011-08-10 14:12:53 CEST] my friend makes a living off of them [2011-08-10 14:18:31 CEST] impressive [2011-08-10 19:16:08 CEST] wait... using fstat() to detect an inode change on a file descriptor that is kept open in the lifetime of ncdc is perhaps not a really good idea [2011-08-10 19:52:13 CEST] hehe [2011-08-10 21:04:23 CEST] apparently teamfair.info went offline, too bad :( [2011-08-10 21:05:23 CEST] that's not the first time [2011-08-10 21:05:33 CEST] although this time it looks as if they lost the domain... [2011-08-10 21:05:36 CEST] ouch [2011-08-10 21:05:37 CEST] yep [2011-08-10 21:05:49 CEST] any other place where the nmdc protocol is detailed? [2011-08-10 21:06:32 CEST] i was trying to understand how passive searching works [2011-08-10 21:06:35 CEST] there is this relatively new project at sourceforge: http://nmdc.svn.sourceforge.net/viewvc/nmdc/trunk/NMDC.txt [2011-08-10 21:06:43 CEST] but I don't think that document is complete yet [2011-08-10 21:07:06 CEST] and it is an edit of the ADC spec, so there's some ADC stuff mixed in probably [2011-08-10 21:08:06 CEST] i've just found that as well :) [2011-08-10 21:08:17 CEST] i should follow wiki right away next time [2011-08-10 21:08:37 CEST] is that project already linked from wikipedia? [2011-08-10 21:08:52 CEST] yep [2011-08-10 21:09:10 CEST] but it seems wrong especially the part about searching [2011-08-10 21:09:18 CEST] ah well i get the idea of how it works [2011-08-10 21:09:20 CEST] must have been the work of the guy who made it, I remember it being announced on the dc dev hub just last week or so :P [2011-08-10 21:11:58 CEST] what's wrong with it? [2011-08-10 21:17:09 CEST] searching doesn't work for me right now and i am trying to find out why [2011-08-10 21:17:19 CEST] most likely my peculiar network setup [2011-08-10 21:17:31 CEST] UDP port forwarded? [2011-08-10 21:17:44 CEST] oh, passive [2011-08-10 21:18:37 CEST] the hub may also be simply ignoring your $Search (yes, hubs ocassionally do that) [2011-08-10 21:19:05 CEST] well the udp port forwarding is possible albeit somewhat crippled [2011-08-10 21:20:19 CEST] yay! raid rebuild finished [2011-08-10 21:20:36 CEST] works something like socat udp-listen:port,fork,reuseaddr tcp:port2 and forward the tcp port [2011-08-10 21:20:45 CEST] congrats [2011-08-10 21:20:58 CEST] it doesn't matter either way if you're passive [2011-08-10 21:21:22 CEST] well that would be the "active" solution [2011-08-10 21:21:36 CEST] it's not working so i fell back to passive which doesn't work either [2011-08-10 21:21:49 CEST] i have to debug where the problem is by going home :) [2011-08-10 21:22:03 CEST] then i can have an active connection and see if that works at least [2011-08-10 21:57:09 CEST] ==46918== Signal 11 being dropped from thread 0's queue [2011-08-10 21:57:15 CEST] does this ring something? [2011-08-10 21:57:49 CEST] my interface crashes on starting it nromally ( i think it's starting to hash) and hangs on valgrind spewing above error to the log [2011-08-10 21:58:39 CEST] you sure know how to find errors I never new were remotely possible >_> [2011-08-10 21:58:56 CEST] but I'm sorry, no idea what that even means [2011-08-10 21:59:09 CEST] (and afk) [2011-08-11 00:28:08 CEST] Read error: Error receiving data: Connection timed out [2011-08-11 00:28:08 CEST] Connection lost. Waiting 30 seconds before reconnecting. [2011-08-11 00:28:38 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:29:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:29:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:30:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:30:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:31:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:31:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:32:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:32:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:33:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:33:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:34:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:34:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:35:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:35:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:36:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:36:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:37:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:37:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:38:14 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:38:44 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:39:14 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:39:44 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:40:14 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:40:44 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:41:14 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:41:44 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:42:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:42:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:43:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:43:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:44:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:44:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:45:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:45:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:46:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:46:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:47:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:47:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:48:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:48:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:49:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:49:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:50:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:50:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:51:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:51:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:52:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:52:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:53:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:53:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:54:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:54:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:55:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:55:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:56:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:56:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:57:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:57:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:58:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:58:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 00:59:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 00:59:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:00:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:00:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:01:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:01:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:02:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:02:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:03:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:03:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:04:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:04:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:05:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:05:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:06:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:06:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:07:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:07:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:08:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:08:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:09:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:09:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:10:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:10:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:11:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:11:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:12:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:12:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:13:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:13:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:14:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:14:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:15:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:15:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:16:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:16:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:17:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:17:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:18:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:18:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:19:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:19:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:20:19 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:20:49 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:21:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:21:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:22:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:22:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:23:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:23:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:24:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:24:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:25:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:25:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:26:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:26:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:27:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:27:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:28:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:28:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:29:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:29:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:30:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:30:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:31:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:31:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:32:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:32:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:33:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:33:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:34:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:34:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:35:24 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:35:54 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:36:29 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:36:59 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:37:29 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:37:59 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:38:29 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:38:59 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:39:29 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:39:59 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:40:29 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:40:59 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:41:34 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:42:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:42:34 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:43:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:43:34 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:44:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:44:34 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:45:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:45:34 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:46:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:46:34 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:47:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:47:34 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:48:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:48:34 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:49:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:49:34 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:50:04 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:50:39 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:51:09 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:51:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:52:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:52:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:53:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:53:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:54:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:54:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:55:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:55:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:56:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:56:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:57:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:57:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:58:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:58:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 01:59:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 01:59:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:00:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:00:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:01:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:01:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:02:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:02:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:03:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:03:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:04:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:04:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:05:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:05:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:06:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:06:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:07:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:07:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:08:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:08:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:09:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:09:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:10:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:10:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:11:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:11:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:12:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:12:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:13:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:13:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:14:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:14:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:15:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:15:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:16:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:16:44 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:17:14 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:17:49 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:18:19 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:18:54 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:19:24 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:19:54 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:20:24 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:20:54 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:21:24 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:21:54 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:22:24 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:22:54 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:23:24 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:23:59 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:24:29 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:24:59 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:25:29 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:25:59 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:26:29 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:26:59 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:27:29 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:27:59 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:28:29 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:28:59 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:29:29 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:30:04 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:30:34 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:31:04 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:31:34 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:32:04 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:32:34 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:33:04 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:33:34 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:34:04 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:34:34 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:35:04 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:35:34 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:36:04 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:36:34 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:37:04 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:37:34 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:38:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:38:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:39:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:39:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:40:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:40:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:41:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:41:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:42:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:42:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:43:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:43:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:44:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:44:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:45:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:45:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:46:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:46:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:47:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:47:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:48:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:48:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:49:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:49:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:50:09 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:50:39 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:51:14 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:51:44 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:52:14 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:52:44 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:53:14 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:53:44 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:54:14 CEST] Could not connect to hub: Socket I/O timed out. Wating 30 seconds before retrying. [2011-08-11 02:54:44 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 02:54:44 CEST] Connected to 188.142.33.141:2780. [2011-08-11 02:54:44 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-08-11 02:54:44 CEST] Welcome to the ncdc development hub! [2011-08-11 02:54:44 CEST] [2011-08-11 02:54:44 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-08-11 02:54:44 CEST] [2011-08-11 02:54:44 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-08-11 02:54:44 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-08-11 02:54:44 CEST] [2011-08-11 02:54:44 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-08-11 02:54:44 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-08-11 02:54:44 CEST] [2011-08-11 02:54:44 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-08-11 02:54:44 CEST] [2011-08-11 02:54:44 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-08-11 02:54:44 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-08-11 02:54:44 CEST] [2011-08-11 11:56:31 CEST] I'm moving the hub to a more stable server [2011-08-11 11:57:04 CEST] until the DNS has updated, you can connect to adc://blicky.net:2780/ [2011-08-11 11:59:25 CEST] Read error: Remote disconnected. [2011-08-11 11:59:25 CEST] Connection lost. Waiting 30 seconds before reconnecting. [2011-08-11 11:59:55 CEST] Connecting to dc.blicky.net:2780... [2011-08-11 11:59:56 CEST] Connected to 194.50.163.173:2780. [2011-08-11 11:59:56 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-08-11 11:59:56 CEST] Welcome to the ncdc development hub! [2011-08-11 11:59:56 CEST] [2011-08-11 11:59:56 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-08-11 11:59:56 CEST] [2011-08-11 11:59:56 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-08-11 11:59:56 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-08-11 11:59:56 CEST] [2011-08-11 11:59:56 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-08-11 11:59:56 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-08-11 11:59:56 CEST] [2011-08-11 11:59:56 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-08-11 11:59:56 CEST] [2011-08-11 11:59:56 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-08-11 11:59:56 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-08-11 11:59:56 CEST] [2011-08-11 20:45:32 CEST] tmux sure wins when working with multiple sessions [2011-08-11 20:46:08 CEST] ** Yorhel is trying tmux [2011-08-11 23:49:48 CEST] ** kaste loves tmux [2011-08-11 23:55:56 CEST] ** xmw listens to Bad Religon - I love my Compute [2011-08-12 00:08:48 CEST] you're probably asleep but this is the valgrindlog for yesterdays segfault where [2011-08-12 00:09:48 CEST] that message occured about the signal being dropped when starting to hash http://tehsuck.de/paste/index.php?show=4 [2011-08-12 10:06:21 CEST] thanks, I'll have a look at it in a bit [2011-08-12 10:09:00 CEST] hmm, if I automatically attach a tmux session by calling 'roxterm -e ..' from my WM config, all non-ASCII characters are being replaced with an underscore [2011-08-12 10:09:42 CEST] manually detaching and attaching works, so I guess some environment variables aren't being set [2011-08-12 10:31:01 CEST] diff the envs? [2011-08-12 10:32:48 CEST] looks like the problem isn't with starting from the WM, but using ssh .. -t command [2011-08-12 10:32:58 CEST] and $LANG is indeed not being set that way [2011-08-12 11:32:18 CEST] I can't immediately find a reason for that invalid read in your valgrind log [2011-08-12 11:39:55 CEST] in fact, is looks rather strange, around the ui_draw() code there is only a single mvprintw() called with a %s format, and that is a statically allocated string... [2011-08-12 11:42:18 CEST] I guess I should steal my friends' macbook for a bit to play around with it [2011-08-12 12:29:02 CEST] it's more likely to not be a macos issue but rather the custom built libs, ncurses and a few others aren't shipped by apple and users install them via macports, fink, homebrew, ... and they tend to be different [2011-08-12 12:33:53 CEST] I used to have a macbook myself, so I'm a bit familiar with the mess [2011-08-12 13:53:26 CEST] gah, glib is spamming my valgrind logs with errors after a system upgrade :( [2011-08-12 13:53:46 CEST] time to start using an ignore file [2011-08-12 14:05:23 CEST] write a patch and submit it instead :p [2011-08-13 01:54:32 CEST] Connecting to dc.blicky.net:2780... [2011-08-13 01:54:32 CEST] Connected to 194.50.163.173:2780. [2011-08-13 01:54:32 CEST] This hub is running ADCH++ v2.7.0 (r0) Release [2011-08-13 01:54:32 CEST] Welcome to the ncdc development hub! [2011-08-13 01:54:32 CEST] [2011-08-13 01:54:32 CEST] Check out the homepage for the latest version of ncdc and other news. [2011-08-13 01:54:32 CEST] [2011-08-13 01:54:32 CEST] Homepage: http://dev.yorhel.nl/ncdc [2011-08-13 01:54:32 CEST] Git repo: http://g.blicky.net/ncdc.git/ [2011-08-13 01:54:32 CEST] [2011-08-13 01:54:32 CEST] Ohloh: https://www.ohloh.net/p/ncdc [2011-08-13 01:54:32 CEST] Freshmeat: http://freshmeat.net/projects/ncdc [2011-08-13 01:54:32 CEST] [2011-08-13 01:54:32 CEST] This is a chat-only hub, sharing and searching has been disabled. [2011-08-13 01:54:32 CEST] [2011-08-13 01:54:32 CEST] Feel free to leave a message even when nobody is available, I (Yorhel) will eventually [2011-08-13 01:54:32 CEST] read it. Of course, you should keep your client running if you want a reply. :-) [2011-08-13 01:54:32 CEST] [2011-08-13 02:00:39 CEST] k, i get an segfault reading backlog #0 0x00007ffff6013022 in _IO_vfprintf_internal (s=, format=, ap=) at vfprintf.c:1599 [2011-08-13 02:00:39 CEST] #1 0x00007ffff60bb8b5 in __vasprintf_chk (result_ptr=0x7fffffffd008, flags=1, [2011-08-13 02:00:39 CEST] format=0x80ade0 "[2011-08-12 11:39:55 CEST] in fact, is looks rather strange, around the ui_draw() code there is only a single mvprintw() called with a %s format, and that is a statically allocated string...", args=0x7fffffffd490) at vasprintf_chk.c:68 [2011-08-13 02:00:39 CEST] #2 0x00007ffff6fc254b in vasprintf (string=0x7fffffffd008, format=, args=) at /usr/include/bits/stdio2.h:199 [2011-08-13 02:00:39 CEST] #3 g_vasprintf (string=0x7fffffffd008, format=, args=) at gprintf.c:318 [2011-08-13 02:00:39 CEST] #4 0x00007ffff6f9dbc0 in g_strdup_vprintf (format=, args=) at gstrfuncs.c:255 [2011-08-13 02:00:39 CEST] #5 0x00007ffff6f87201 in g_logv (log_domain=0x0, log_level=, [2011-08-13 02:00:39 CEST] format=0x80ade0 "[2011-08-12 11:39:55 CEST] in fact, is looks rather strange, around the ui_draw() code there is only a single mvprintw() called with a %s format, and that is a statically allocated string...", args1=0x7fffffffd4f0) at gmessages.c:524 [2011-08-13 02:00:39 CEST] #6 0x00007ffff6f875d3 in g_log (log_domain=, log_level=, format=) at gmessages.c:577 [2011-08-13 02:00:39 CEST] #7 0x0000000000420917 in ui_logwindow_load (lw=0x8062f0, fn=0x8027b0 "/home/michael/.ncdc/logs/#ncdc.log", num=100) at ui_util.c:96 [2011-08-13 02:00:39 CEST] #8 0x0000000000420afc in ui_logwindow_create (file=0x6e2440 "#ncdc", load=100) at ui_util.c:131 [2011-08-13 02:00:39 CEST] #9 0x0000000000417754 in ui_hub_create (name=0x6e2496 "ncdc", conn=1) at ui.c:241 [2011-08-13 02:00:39 CEST] #10 0x0000000000410f4e in c_open (args=0x6e2496 "ncdc") at commands.c:918 [2011-08-13 02:00:39 CEST] #11 0x0000000000412c3b in cmd_handle (ostr=0x7fec60 "/open ncdc") at commands.c:1668 [2011-08-13 02:00:39 CEST] #12 0x000000000041720c in ui_main_key (key=8589934698) at ui.c:138 [2011-08-13 02:00:39 CEST] #13 0x000000000042050a in ui_input (key=8589934698) at ui.c:2158 [2011-08-13 02:00:39 CEST] #14 0x00000000004081a2 in handle_input () at main.c:139 [2011-08-13 02:00:39 CEST] #15 0x0000000000408204 in stdin_read (src=0x7ffff0000a10, cond=G_IO_IN, dat=0x0) at main.c:149 [2011-08-13 02:00:39 CEST] #16 0x00007ffff6f7e6ee in g_main_dispatch (context=0x6e2270) at gmain.c:2441 [2011-08-13 02:00:39 CEST] #17 g_main_context_dispatch (context=0x6e22