Actually, it is surprisingly easy to abuse FTP... and hammer the server beyond all recognition. I've seen it. It's ugly.
A lot of FTP transfers get started... but never get past the login phase. It does one *bleep* of a job in gnawing at the pool of sockets but isn't that friendly CPU-wise. I didn't do enough deep diving in the performance data whilst it was happening to see where those cycles were going. I forgot which Windoze client the customer was using when they spun into a loop starting FTP sessions and not getting to the login portion on one of our interchange servers. I was surprised how little it took to make other FTPs unable to be performed. I have *no* idea if a "real" Linux (or Unix) based client can be made to misbehave this way without some creative jiggery-pokery (you know "doinking") with the source code. -soup -- John R. Campbell Speaker to Machines souperb at gmail dot com MacOS X proved it was easier to make Unix user-friendly than to fix Windows ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
