code logs -> 2011 -> Tue, 18 Jan 2011< code.20110117.log - code.20110119.log >
--- Log opened Tue Jan 18 00:00:09 2011
--- Day changed Tue Jan 18 2011
00:00 You're now known as TheWatcher[zZzZ]
00:25 ComradeBear [ZLOK@3A600C.A966FF.5BF32D.8E7ABA] has joined #code
00:40
< Alek>
"Our accountants pass around legends of a key combo that switches NumPad to roman numerals."
00:41
< gnolam>
Heh. From where?
00:43
< Alek>
bash.org.ru
01:03 Attilla [Some.Dude@Nightstar-735cedc6.threembb.co.uk] has quit [Ping timeout: 121 seconds]
01:08 Vornicus-Latens is now known as Vornicus
01:20 gnolam [lenin@Nightstar-38637aa0.priv.bahnhof.se] has quit [[NS] Quit: Z?]
01:32 Syloqs-AFH [Syloq@NetworkAdministrator.Nightstar.Net] has quit [[NS] Quit: ]
01:45 Syloqs_AFH [Syloq@NetworkAdministrator.Nightstar.Net] has joined #code
01:46 Syloqs_AFH is now known as Syloqs-AFH
01:53 Rhamphoryncus [rhamph@Nightstar-473f8685.abhsia.telus.net] has joined #code
02:12 ComradeBear [ZLOK@3A600C.A966FF.5BF32D.8E7ABA] has quit [Ping timeout: 121 seconds]
05:01 Vornicus [vorn@ServerAdministrator.Nightstar.Net] has quit [[NS] Quit: Leaving]
05:08 Vornicus [vorn@ServerAdministrator.Nightstar.Net] has joined #code
05:08 mode/#code [+o Vornicus] by Reiver
05:33 Kindamoody[zZz] is now known as Kindamoody
05:46 Kindamoody is now known as Kindamoody|out
06:11 AnnoDomini [annodomini@Nightstar-51464ec2.adsl.tpnet.pl] has joined #code
06:11 mode/#code [+o AnnoDomini] by Reiver
06:19 celticminstrel [celticminst@Nightstar-f8b608eb.cable.rogers.com] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
06:26 Tarinaky [Tarinaky@Nightstar-f349ca6d.plus.com] has quit [Client closed the connection]
06:35 Derakon is now known as Derakon[AFK]
07:11 You're now known as TheWatcher
08:02 ComradeBear [ZLOK@3A600C.A966FF.5BF32D.8E7ABA] has joined #code
08:11 You're now known as TW[jurying]
08:41 Vornicus is now known as Vornicus-Latens
09:21 ComradeBear [ZLOK@3A600C.A966FF.5BF32D.8E7ABA] has quit [Ping timeout: 121 seconds]
09:52 ComradeBear [ZLOK@26ECB6.A4B64C.298B52.D80DA0] has joined #code
10:20 AnnoDomini [annodomini@Nightstar-51464ec2.adsl.tpnet.pl] has quit [[NS] Quit: Need to flee.]
11:00 AnnoDomini [annodomini@F67919.F326B3.98D923.BDA7B6] has joined #code
11:00 mode/#code [+o AnnoDomini] by Reiver
11:08 Kindamoody|out is now known as Kindamoody
12:33 cpux is now known as shade_of_cpux
12:37
< ComradeBear>
Anybody around?
12:38
< ComradeBear>
Nevermind, it'll be an hour.
12:38
< ComradeBear>
I'll be back!
12:52 AnnoDomini [annodomini@F67919.F326B3.98D923.BDA7B6] has quit [[NS] Quit: GO INTO DEBT.]
12:54 gnolam [lenin@Nightstar-38637aa0.priv.bahnhof.se] has joined #code
13:26 AnnoDomini [annodomini@Nightstar-51464ec2.adsl.tpnet.pl] has joined #code
13:26 mode/#code [+o AnnoDomini] by Reiver
13:29 You're now known as TheWatcher
14:12
< Phox>
You know, it's been an hour, and he never returned.
15:25
< froztbyte>
Yo mamma so fat, she sat on a binary tree and flattened it into a linked list in O(1) time.
15:26
<@jerith>
Dammit! I wanted to paste that here after you put it in Other Places.
15:26
< froztbyte>
:D
15:37
< EvilDarkLord>
Wait. Even if the momma is that fat, wouldn't she need sqrt(log(n)) time to fall through the tree?
15:39
< Rhamphoryncus>
<kerio> and of course chuck norris' programs all run in O(1/n)
15:56 * AnnoDomini suspects Rhamphoryncus visits Freenode.
15:56 * Rhamphoryncus suspects so as well
16:16 Attilla [Some.Dude@Nightstar-782ef12e.threembb.co.uk] has joined #code
16:17 mode/#code [+o Attilla] by Reiver
17:30 Tarinaky [Tarinaky@Nightstar-f349ca6d.plus.com] has joined #code
18:01 AnnoDomini is now known as Lykkennan
18:01 Attilla is now known as Prophet
18:16 EvilDarkLord is now known as Maze
18:21
<@ToxicFrog>
I've only been doing it for ten minutes and I already know I don't like marking assignments.
19:00 SmithKurosaki [smith@Nightstar-bd012c7e.dsl.teksavvy.com] has quit [Operation timed out]
19:01 Rhamphoryncus [rhamph@Nightstar-473f8685.abhsia.telus.net] has quit [Client exited]
19:08 DBot [Reiver@Nightstar-8470770e.xnet.co.nz] has joined #code
19:10 DiceBot [Reiver@Nightstar-8470770e.xnet.co.nz] has quit [Ping timeout: 121 seconds]
19:11 DBot is now known as DiceBot
19:11
<@ToxicFrog>
Oh god
19:12
<@ToxicFrog>
There's a depressing number of people who interpreted the first question very, very wrong.
19:12
<@ToxicFrog>
It asks for two switching circuits, one implementing (A+B+C) and one implementing (AB)+(AC)+(BC).
19:13
<@ToxicFrog>
At least two people created logic circuits, and a bunch of others created one circuit that implements one (or in some cases neither) of those functions.
19:18 SmithKurosaki [smith@Nightstar-bd012c7e.dsl.teksavvy.com] has joined #code
19:20 Tarinaky [Tarinaky@Nightstar-f349ca6d.plus.com] has quit [Operation timed out]
19:42 AbuDhabi [annodomini@Nightstar-6cff53d6.adsl.tpnet.pl] has joined #code
19:42 AbuDhabi is now known as Lykkennan_
19:44 Lykkennan [annodomini@Nightstar-51464ec2.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
20:05 Lykkennan_ is now known as AnnoDomini
20:18 celmin [celticminst@1AB00B.855209.A256BB.43A6F1] has joined #code
20:19
< celmin>
Question, if any Python people are around... is there a security risk inherent in the map() command?
20:24 celmin [celticminst@1AB00B.855209.A256BB.43A6F1] has quit [Ping timeout: 121 seconds]
20:31 celmin [celticminstre@1AB00B.855209.A256BB.457AC8] has joined #code
20:35 celmin [celticminstre@1AB00B.855209.A256BB.457AC8] has quit [Ping timeout: 121 seconds]
20:36
< ComradeBear>
151220 | <Phox> You know, it's been an hour, and he never returned. <- That is true, that's because the issue didn't return within the hour.
20:36
< ComradeBear>
I was going to ask for help bugtesting a site, but the admin I'm helping decided he'd rather eat chips.
20:36
< ComradeBear>
(Or something.)
20:37
<@jerith>
Eating chips is more fun than debugging.
20:37
< ComradeBear>
Heh. :D
20:37 * jerith sometimes eats chips /while/ he debugs.
20:37
< ComradeBear>
In my defense, I never actually left. So I couldn't return.
20:38
< ComradeBear>
Anyways, it turned out I didn't need any help being an idiot.
20:38
<@jerith>
You can do that all on your own?
20:38
< ComradeBear>
So it would seem.
20:38
< ComradeBear>
I should become a professional idiot.
20:39
<@jerith>
Is there much money in it?
20:40
< ComradeBear>
Doubt it.
20:40
< ComradeBear>
Right now I'm performing for a flask of campaigne I'm not going to drink.
20:43
<@jerith>
Is it the prize or the audience?
20:45
< ComradeBear>
The prize.
21:05 Vornicus-Latens is now known as Vornicus
21:13 Maze is now known as EvilDarkLord
21:19
<@Vornicus>
celmin: map()? Like, throwing a list through a function? Not unless you distrust an arbitrary function, which means you wouldn't be able to trust, well, /anything/
22:04 Syloqs-AFH [Syloq@NetworkAdministrator.Nightstar.Net] has quit [[NS] Quit: ]
22:23 Prophet is now known as Attilla
22:27
< simon_>
is f(f(x)) = x a consequence of reflexivity, or what is it called?
22:29
<@Vornicus>
That is called "self inverse"
22:30
< simon_>
oh ok.
22:30
<@Vornicus>
f(x(x)) = f(x) is idempotence.
22:31
< simon_>
f(x(x)) = f(x) implies that x is a function?
22:32
< simon_>
oh, you mean f(f(x)). I get it.
22:33
<@Vornicus>
er, right, typos
22:33
< simon_>
hmmm
22:34
< simon_>
so a a unary function can be idempotent in itself for a set of things, and a non-unary function can be (left/right) idempotent given a subset of idempotent elements of a set of things.
22:35
< simon_>
s/non-unary/binary/ I don't really now about tertiary operators, I don't suppose they're that common.
22:36
<@Vornicus>
well, a function's parameters can be made a single object via a tuple.
22:38
< simon_>
yes, I was thinking mathematically.
22:43 Syloqs_AFH [Syloq@NetworkAdministrator.Nightstar.Net] has joined #code
22:44 Syloqs_AFH is now known as Syloqs-AFH
22:52 Syloqs-AFH [Syloq@NetworkAdministrator.Nightstar.Net] has quit [[NS] Quit: ]
22:56 Syloqs_AFH [Syloq@NetworkAdministrator.Nightstar.Net] has joined #code
22:57 Syloqs_AFH is now known as Syloqs-AFH
23:08 gnolam [lenin@Nightstar-38637aa0.priv.bahnhof.se] has quit [[NS] Quit: Z?]
23:27 Derakon [chriswei@Nightstar-cfae48c3.ca.comcast.net] has joined #code
23:27 mode/#code [+o Derakon] by Reiver
23:27
<@Derakon>
I have an SSH connection that has a process running in the background that's spitting out status information to stdout (despite my attempt to capture it with "2>&1 > log.txt").
23:28
<@Derakon>
If I log out and then log back in in a different session, the process will continue running; is there any way to get back access to that status information?
23:33
<@Vornicus>
screen, is the usual tool.
23:34
<@Derakon>
Given that I haven't started this in screen?
23:34
<@ToxicFrog>
How will it continue running?
23:34
<@ToxicFrog>
Generally you aren't allowed to log out when you have backgrounded jobs, and if you force it they'll SIGPIPE.
23:35
<@Derakon>
...
23:35
<@ToxicFrog>
Also, the reason your capture didn't work is that you got the order wrong: >log.txt 2>&1
23:35
<@Derakon>
I wasn't prevented from logging out last week when I tried this.
23:35
<@Derakon>
And when I logged back in this morning I could see that the CPU was pegged.
23:35
<@ToxicFrog>
Huh. How did you background it?
23:36
<@Derakon>
Um...can't remember if that was ctrl-Z + bg or just '&' at the end of the invocation.
23:36
<@Derakon>
The ones I have right now are &.
23:36
<@Derakon>
Should've just used the job queue and had done with it...dammit.
23:36
<@ToxicFrog>
Huh. That totally works.
23:36
<@ToxicFrog>
I guess it only complains if the jobs are suspended.
23:37
<@Derakon>
That makes a modicum of sense.
23:37
<@Derakon>
It'd be all too easy to leave suspended jobs forgotten until the end of time otherwise.
23:37
<@ToxicFrog>
Yeah.
23:38
<@Derakon>
You had me worried there that the reason those jobs hadn't terminated was because they had hung, instead of because they're ridiculously CPU-intensive.
23:39
<@Derakon>
(Running data processing on 750 megapixels' worth of data)
23:41
< froztbyte>
Derakon: untested solution that I thought of the other day
23:41
< froztbyte>
(to your process question)
23:41
< froztbyte>
is to suspend it on the one side with cryopid, then resume it from within a screen
23:41
< froztbyte>
you're welcome to test it out and see if it actually does anything useful ;)
23:42
<@Derakon>
Okay, from what I can read of cryopid it involves copying program state so you can transfer it across sessions?
23:42
<@Derakon>
That would probably not work very well here...
23:42
< froztbyte>
yeah, memory dump to file, or somesuch
23:42
<@Derakon>
See also: 750 megapixels' worth of data.
23:43
<@Derakon>
(And multiple copies of that data in memory, from what a coworker has said)
23:43
< froztbyte>
so the usual endian and arch concerns alongside memory constraints and all that shit
23:43
< froztbyte>
Derakon: yeah, I guess you're possibly screwed for right now :)
23:44
<@Derakon>
Oh well...
23:44
<@ToxicFrog>
Derakon: you might be able to do something with /proc/<pid>/fd/*
23:44
< froztbyte>
meh..time for me to lock up fort knox again and go get some sleep, I guess
23:44
<@Derakon>
I still have a couple of days to get this processed, and it's on the second-most-intensive step now having started this morning.
23:44
<@Derakon>
Night, Frozt.
23:44
< froztbyte>
\o all
23:44
<@ToxicFrog>
In particular, fd/1 and fd/2 will be stdout and stderr, and catting them sometimes works (at the cost of interfering the program's "normal" output, but right now that's not connected to anything)
23:45
<@Derakon>
(Boss can't understand why this is taking so long. I keep telling him that we're using -iter=5 instead of -iter=4 and that runtime depends exponentially on that value, he keeps ignoring me)
23:45
<@ToxicFrog>
Failing that, I've got no ideas other than "run it in screen next time"
23:46
<@Derakon>
The problem I have with screen is that it mucks with vim...or at least, that's what I remember from last time I tried it.
23:46
<@Derakon>
So I don't use it by default, and I don't think to fire it up for long-running stuff.
23:47
<@ToxicFrog>
There's probably some option you can pass in that will fix that
23:47
< Namegduf>
I've never had it muck with vim, so it's probably a configuration-specific thing you can fix.
23:47
<@ToxicFrog>
Failing that...yeah, use it for long-running programs and run vim normally.
23:47 * Namegduf uses vim for a lot
23:48
<@Derakon>
It's my text editor of choice, and I don't generally use an IDE.
23:49
<@ToxicFrog>
Derakon: incidentally, expanding on the output redirection - x>y is basically "fd[x] = open(y)", and x>&y is "fd[x] = fd[y]". That's why order matters.
23:49
<@Derakon>
Yeah, I keep forgetting how that works.
23:49
<@Derakon>
Part of the problem being that I have "2>&1|less" encoded in my muscle memory.
23:50
<@Derakon>
Hrm...catting proc/foo/fd/1 and proc/foo/fd/2 doesn't seem to be capturing this output.
23:50
<@Derakon>
Mind, I do still have the original session that started the process open.
23:51
<@Derakon>
So maybe that has a claim on the file descriptors.
23:51
<@ToxicFrog>
Oh
23:52
<@Derakon>
Hmm...and having closed that session, now I get "Input/output error" when I try to cat it.
23:52
<@Derakon>
("it" being /proc/foo/fd/*)
23:52
<@ToxicFrog>
Welp
23:53
<@Derakon>
ls -l on the fds says they redirect to "/dev/pts/1 (deleted)"
23:53
<@Derakon>
So much for that idea!
23:56
<@Derakon>
The problem I have here is that I now have no way to verify that the program is healthy.
23:57
<@Derakon>
I don't want to throw away ~8 hours' worth of processing time, especially since I have no idea how long it'll take to finish and my boss needs this data before he leaves on a trip on Friday...
23:57
<@Derakon>
Wish I'd gotten the damned redirect done properly when I started this.
--- Log closed Wed Jan 19 00:00:56 2011
code logs -> 2011 -> Tue, 18 Jan 2011< code.20110117.log - code.20110119.log >