[scabbage]

I have access to a Mac machine running Panther 10.3.6 using ssh. In order to be able to use BitTorrent remotely, I followed all the steps in this post. By the way, I use the Python source from here because I wish to use it on command line. My Python came with Panther and my wxPython is from here . Now, my problem is when I run this command to have several (like 6 or 7) downloads running

Code:
screen btdownloadcurses.py --display_interval 5 mytorrent.torrent

and all are detached. When I try to attach the screen back to one of them, say

Code:
screen -r 5968

the system crashes. Pretty bad, too. My ssh just freezes and the whole server is down. I'll have to go be to the Mac machine to reboot it. By the way, the crash didn't happen as soon as I attach the first screen. I attached, detached and attached another and then it crashed. Can anyone explain what has happened? Thanks.

[galarneau]

I don't have an answer as to why it's crashing, but I would try using screen a different way, as follows:

1) log into the remote Mac
2) type 'screen' to start a new screen session
3) start the first bittorrent download
4) create a new terminal in screen (type ctrl-a then c)
5) start the next bittorrent download
6) loop back to #4 until you have all your downloads going
7) detach from screen (ctrl-a then d)
8) when you want to log back in to the remote mac, type 'screen -rd' to get back to your session

This way, all your downloads are running inside a single screen session that contains multiple virtual terminals, so it's much easier to manage.

Some other handy screen commands are:
ctrl-a then A to rename a terminal
ctrl-a then n to show the next terminal (or p for the previous one)
ctrl-a then " to show a list of all terminals

Hope this helps. Screen is a great program, so it pays to spend some time learning it.

[scabbage]

Thanks for the advice. I should have tried that. I was wondering if the crash has anything to do with screensaver or power management that kind of stuff. Any idea?

[galarneau]

I can't say for sure, but I doubt the problem is with a screensaver/power management issue, but more likely a bug in screen itself.

I've only used it in the context of ssh'ing into my remote OpenBSD box from my Mac, and running screen from there. No problems whatsoever.

You might try a different version of screen (e.g. from Darwin Ports or Fink) and see if the problem persists. Also, you might think about grabbing an old Pentium 166 or something, and running one of the *BSD's on it for remote Bittorrent'ing. Not only is it a practical use for old almost free hardware, but a great learning experience on what makes *BSD's tick. I've had a ton of fun setting mine up (I call it my BitchBox, because it just sits there and does what I tell it to do)</misogynist>

I find it somewhat strange that you only run one terminal window in each screen session though.... why not just make one screen session as I described above, and run multiple virtual terminals inside that? I bet it would be less likely to crash on you.

Anyway, hope this has been of some help.

[scabbage]

I find it somewhat strange that you only run one terminal window in each screen session though.... why not just make one screen session as I described above, and run multiple virtual terminals inside that? I bet it would be less likely to crash on you.

That was because I didn't know how to use screen at all. After reading through the man page of screen, I realized how silly it was to have used screen like that (screen is surely one of the coolest programs). Now, I'm only running one screen session with multiple terminal windows and the crashing problem disappeared.

Also, you might think about grabbing an old Pentium 166 or something, and running one of the *BSD's on it for remote Bittorrent'ing. Not only is it a practical use for old almost free hardware, but a great learning experience on what makes *BSD's tick. I've had a ton of fun setting mine up (I call it my BitchBox, because it just sits there and does what I tell it to do)</misogynist>

That's something I want to do too, except for my room is in a mess right now and really don't have any room for another box. But I'll definitely give it a try when I move to another apartment. Thanks for being a great help, galarneau.