site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com [mightygorilla:~] tas% ssh yobgorgle Password: Welcome to Darwin! [yobgorgle:~] tas% ls tcsh: Out of memory. Connection to yobgorgle closed. [mightygorilla:~] tas% Wow. I just don't know what to say. Nothing appears in system.log or /cores, by the way. Anybody have any suggestions before I file a bug? _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... So I'm on my Powerbook (10.4.1), and SSH across the good old domestic WLAN to my G5 (Also 10.4.1). I get behavior like this: Some shell commands do succeed, but most fail identically to this example with ls. Bizarre thing #1: the G5 named "Yobgorgle" had roughly 2GB free RAM at the time of this event. Physical memory certainly isn't a problem. The only justification for the error in question is if some piece of code tried to allocate more address space than the kernel was willing to give a single process. Bizarre thing #2: So, "yobgorgle" is really "yobgorgle.local" since I have "local" in my search domains list. In other words, it's a Ren^h^h^h Bonjour name. On a whim, I decided to SSH to the actual IP address: [mightygorilla:~] tas% ssh 192.168.1.40 Password: Welcome to Darwin! [yobgorgle:~] tas% ls Applications/ Documents/ Movies/ Public/ bin/ Desktop/ Library/ Pictures/ Temporary Items/ [yobgorgle:~] tas% Bizarre thing #3: Everything seems to work normally when I SSH in the opposite direction, regardless of whether I use the Bonjour name or the IP address of the PowerBook. The only remotely relevant difference in configuration which I can think of is that the PowerBook gets its IP address via DHCP whereas the G5 has a static IP. My brain hurts. Why should the shell (or alternately the programs it's invoking) care how the network name lookup for setup of the SSH session it's communicating through took place? And how can this behavior happen on one machine and not the other? This email sent to site_archiver@lists.apple.com