Apple's built-in FTP server, which is started by clicking a button in the Sharing prefs panel, is probably sufficient for most users. It gives easy access to your machine via FTP, but has some limitations. If you wish to allow others to FTP to your machine, you need to create an OS X account for each user. If you want those users restricted to their home directory, you need to create an 'ftpchroot' file that limits their access. Other more advanced tasks, such as space limitations, require further tweaking to the FTP server.
If you'd like an easy way to put a more robust FTP server solution in place, check out CrushFTP by Ben Spink. CrushFTP is a Java-based application that runs on OS X (and OS 9!).
It has a wealth of options, including:
User (add/delete/modify) management within CrushFTP
Set disk quotas and other privileges by directory
Set maximum idle and connect times and bandwidth limits
Limit max downloads per session
Easily specify which port CrushFTP will serve from
Control which days a user may connect
Limit or allow connections based on IP address
Generate detailed usage reports
I ran a very simple speed comparison this afternoon (transfer one 7.9mb file from my Mac to my Win2000 laptop), and I was surprised to find that CrushFTP beat the built-in FTP server (444K per second vs. 440K per second). A more extensive test would have to be done on multiple files to verify the results, but CrushFTP seems to be just as speedy as the bundled FTP server -- at least in a single-user scenario.
CrushFTP is a $20 shareware application, and it's a fully try-before-you-buy package. If you're looking for a more advanced FTP server package, check it out.
NOTE: I am not a registered CrushFTP user, as my FTP needs are simple. It just seems like a well-developed alternative to the bundled OS X FTP server, with easily defined options. As with anything that allows direct access to your machine, please make sure you're comfortable with the product and its background before installing or using it!
If you're interested in seeing what things get sent out by your machine (for example, hidden data sent out as part of a software install or what cookies are getting set while browsing), check out tcpflow. tcpflow is a packet sniffer for unix-based operating systems. It's got more features than tcpdump (which is included with OS X). Marc Liyanage has created a Mac OS X installer package, which is available here:
If you'd like to get PostgreSQL and PHP running on Mac OS X, the following tutorial should help. Please refer to my previous instructions on installing Apache, PHP, MySQL in this web site to make these instruction clearer.
- Vip Malixi.
[Read the rest of the article for the step-by-step instructions]
I tried to reset the password with the CD, didn't work. I tried the method mentioned here, boot into single user etc. When I used this method, the computer couldn't find the file, ie no such user root, or System Administrator, or my login name. I am currently using X from my second (slowwwww) drive and am trying to avoid doing a new install. Any help would be appreciated.
[Editor's note: Anyone seen anything like this? It appears that the Users data is either missing or damaged, based on James' description of the symptoms...but that's a semi-wild guess on my part...]
Over in this MacNN forum thread, 'JoeyA' identified a rename bug in the Finder, which I've verified on my machine.
If you have a filename that is less than six characters in length and starts with a number, then you cannot modify the name to start with a zero. If you try in the Finder, the name will revert to the previous setting. The only workaround in the Finder is to lengthen the name to at least six characters and then add the zero (this can be one step). After the change is made, then you can re-shorten the name.
Alternatively, you can rename the file in the Terminal with (for example) "mv 3abcd 03abcd" and it will work fine.
Admittedly, this bug won't hit most of us, but if you're having trouble renaming a file with a leading zero, this appears to be the cause.
I' m about to get an Alcatel ADSL modem in two weeks; the connection is PPPoA going through the USB modem. As far as I can find there are no drivers yet for this (a link here which is a BT unoffical FAQ.) So has anyone got a USB ADSL Modem working (PPPoE seems to be built into OSX already?, but of course BT requires me to use PPPoA via USB)
On the alcatel website there are drivers for Win32 Mac (Classic) and Linux. Any idea if the Linux can be compiled or another workaround?
There is a problem with my 10.0.4 that is increasingly apparent. Whenever I click on the Connect button in the Internet Connect application (used to dial up a PPP connection), my superb ultrafine preemptive multitasking goes to hell. Everything freezes, nothing responds, only the mouse is moving (rather hopping from place to place). Force quit of course does not appear either if I press cmd-alt-esc. I even rebooted several times, thinking that my OS X simply froze. But if you wait long enough, eventually everything resumes, the Mac dials up the connection and everything is fine. The delay caused is not fixed a varies from time to time.
My guess is there is a delay when setting up the modem with AT commands, some sort of hardware interupt which hogs the system. I have no direct evidence or solution, however.
[Editor's note: Carriage returns inserted, and repetitive "X" characters snipped, to aid readability; this will appear as one line in your log].
If you're seeing this then it's not a threat to your system. It's someone's machine running windows NT 4.0 with IIS 4.0 or 5.0 enabled, Windows 2000 servers, or betas of XP with the Code Red worm running on their box. This probably means they don't know about it and it doesn't hurt us except it bloats your access logs. The information on it can be found at
I have a question. Is there a way to set a deny rule for this with ipfw. Anyone?
Tcpdump is great and I was looking ahead using it. The bigger was my surprise when I could not, because tcpdump does not recognize my PPP internet connection (or better the ppp0 device) as being configured. Apple's Network Utility has the same sort of problem (it shows only en0, even while being on-line via PPP). Here's an example:
[Editor's note: Here's a story of a user experience with a RAM upgrade that was anything but normal. If you upgrade your RAM at some point in the future and are faced with extremely slow system performance, you may want to remember this article's suggested fix...]
I recently installed additional RAM in my G4 450DP running OS X v10.0.4. I went from 640MB (128MB + 2x 256MB DIMMS) to 1128MB by adding a single 512MB DIMM. The installation was NOT routine.
The system ran normally before installation. After installing the DIMM, all system operations were noticeably slow. The boot process took longer than normal and even the insertion point in the login window blinked at a dramatically slower rate than normal. I could type my username and password blind and not see the character echo for close to 2 minutes.
Once logged in, all my login apps would attempt to start and then quit prompting the standard system message. It would take about 3-5 minutes between each app to get the quit-message. At no time was I able to do anything useful in any application. The system was just too slow. The pointer did move as fast as normal...the system was just unresponsive to clicks or drags.
Read the rest of this article for more detail on the troubleshooting Alex did, and his eventual solution...along with a question about why this happened.