[03:03] *** chazchaz_ has quit IRC (Remote host closed the connection)
[03:06] *** chazchaz_ has joined #warrior
[03:10] *** chazchaz_ has quit IRC (Remote host closed the connection)
[04:23] *** aaaaaaaaa has quit IRC (Leaving)
[05:20] *** Wizardcry has joined #warrior
[06:21] *** nertzy2 has quit IRC (hub.efnet.us irc.Prison.NET)
[06:21] *** nertzy has joined #warrior
[12:49] *** sankin has joined #warrior
[15:20] *** toad1 has joined #warrior
[15:21] *** toad has quit IRC (Read error: Operation timed out)
[15:47] <ersi> Wizardcry: Continously? Usually it fixes itself in a short while
[16:40] *** aaaaaaaaa has joined #warrior
[17:28] <Wizardcry> ersi: yes
[17:28] *** Wizardcry is now known as Wizard\
[17:29] *** Wizard\ is now known as WizCry
[17:58] <ersi> WizCry: Are you sure it can reach the 'net in general?
[18:00] <WizCry> It can.
[18:00] <WizCry> I'm currently archiving the old Bungie data, and it's working great.
[18:55] <aaaaaaaaa> Googling hasn't seemed to help, so I though I'd ask here.  How do I pass arguments to a command in a shell script?  I tried run-pipeline $* (as well as "$*" "$@" $@) and each time it spits out "run-pipeline: error: too few arguments"
[18:58] <WizCry> ersi: Started a 4th warrior, now github seems to resolve and update the trackers
[20:15] *** GitHub30 has joined #warrior
[20:15] *** GitHub30 has left 
[20:19] *** GitHub190 has joined #warrior
[20:19] *** GitHub190 has left 
[20:19] *** GitHub145 has joined #warrior
[20:19] *** GitHub145 has left 
[20:21] *** GitHub43 has joined #warrior
[20:21] *** GitHub43 has left 
[20:25] <chfoo> aaaaaaaaa: it seems to work with run-pipeline $@ and script.sh pipeline.py nickname
[20:43] <aaaaaaaaa> I'll try again then.  maybe its a PEBKAC
[20:57] <aaaaaaaaa> thanks, that pointed me in the right direction.  Apparently $@ doesn't work inside functions unless you do some magic.
[21:02] *** sankin has quit IRC (Leaving.)