| Time |
Nickname |
Message |
|
01:03
🔗
|
|
Baljem_ is now known as Baljem |
|
02:48
🔗
|
|
JesseW has joined #warrior |
|
04:43
🔗
|
|
aaaaaaaaa has quit IRC (Leaving) |
|
05:06
🔗
|
|
Chandro has left |
|
05:22
🔗
|
|
JesseW has quit IRC (Read error: Operation timed out) |
|
05:27
🔗
|
|
JesseW has joined #warrior |
|
06:15
🔗
|
|
JesseW has quit IRC (Ping timeout: 615 seconds) |
|
08:21
🔗
|
|
cloudmons has quit IRC (Remote host closed the connection) |
|
08:44
🔗
|
|
phuzion has quit IRC (Ping timeout: 186 seconds) |
|
13:16
🔗
|
|
phuzion has joined #warrior |
|
14:00
🔗
|
|
Start has quit IRC (Quit: Disconnected.) |
|
14:27
🔗
|
|
nertzy has joined #warrior |
|
14:42
🔗
|
|
nertzy has quit IRC (Quit: This computer has gone to sleep) |
|
15:49
🔗
|
|
Fusl has quit IRC (Read error: Operation timed out) |
|
15:50
🔗
|
|
Fusl has joined #warrior |
|
16:12
🔗
|
|
Start has joined #warrior |
|
16:14
🔗
|
|
Start has quit IRC (Client Quit) |
|
16:17
🔗
|
|
chfoo has quit IRC (Ping timeout: 310 seconds) |
|
16:19
🔗
|
|
Start has joined #warrior |
|
16:19
🔗
|
|
chfoo has joined #warrior |
|
16:20
🔗
|
|
svchfoo3 sets mode: +o chfoo |
|
16:46
🔗
|
|
Coderjoe_ has joined #warrior |
|
16:47
🔗
|
|
Coderjoe has quit IRC (Read error: Operation timed out) |
|
17:04
🔗
|
|
Start has quit IRC (Quit: Disconnected.) |
|
18:34
🔗
|
|
nertzy has joined #warrior |
|
18:55
🔗
|
|
nertzy has quit IRC (Quit: This computer has gone to sleep) |
|
19:18
🔗
|
|
nertzy has joined #warrior |
|
19:21
🔗
|
|
aaaaaaaaa has joined #warrior |
|
19:22
🔗
|
|
svchfoo1 sets mode: +o aaaaaaaaa |
|
20:13
🔗
|
|
Start has joined #warrior |
|
21:16
🔗
|
|
Start has quit IRC (Quit: Disconnected.) |
|
21:55
🔗
|
|
xero has joined #warrior |
|
21:58
🔗
|
xero |
Hi guys. Started using warrior a few days ago and have done about 20GB or so for gamefront and yuku. I wanted to know if there is specific command line syntax to control rate limiting on Mac OS X. The 2 ways listed on archiveteam.org have no affect. Thanks. |
|
22:01
🔗
|
aaaaaaaaa |
Maybe this works? https://www.virtualbox.org/manual/ch06.html#network_bandwidth_limit |
|
22:03
🔗
|
xero |
thanks, checking... |
|
22:16
🔗
|
xero |
those first 3 lines in 6.10 went through (I changed to 300K) but doesn't seem to have worked. Not sure if this is only limiting the upload though. The upload is the only problem I have. I can max around 3.5MB/sec down, but upload I max out at around 650-700K/sec, and when that happens it prevents any other web activity until it finishes. |
|
22:17
🔗
|
xero |
will see what happens when I hit the upload stage. |
|
22:17
🔗
|
xero |
I just want to work this out so I can leave warrior running 24/7 |
|
22:19
🔗
|
aaaaaaaaa |
the rate limit only works on the upload. Download is unaffected by them. |
|
22:19
🔗
|
xero |
ah cool. |
|
22:30
🔗
|
|
nertzy has quit IRC (Quit: This computer has gone to sleep) |
|
22:36
🔗
|
xero |
thanks for the info. so far seems to have sort of worked, though it seems limited to 40K instead of 300K |
|
22:41
🔗
|
aaaaaaaaa |
the command line limit is in bits per second, not bytes. |
|
22:41
🔗
|
aaaaaaaaa |
so the limit you put in was 300 kilobits, not kilobytes |
|
22:47
🔗
|
|
Muad-Dib has quit IRC (Ping timeout: 252 seconds) |
|
22:52
🔗
|
xero |
I put 300K large K |
|
22:56
🔗
|
xero |
could have sworn the docs on archiveteam said large K was for bytes |
|
22:58
🔗
|
xero |
well that was odd, I sent the command through 2 more times and then it worked :P |
|
23:00
🔗
|
xero |
anyway, thanks for the help. Now I can let this crank day and night |
|
23:00
🔗
|
|
Muad-Dib has joined #warrior |
|
23:45
🔗
|
|
Start has joined #warrior |