100% certain way to crash any PB/OS X combo

[hadek]

[I had to edit the original post because people didn't understand my frustrated language]

What happens is this:
Two computers: A (any box) and PB.

I open a lid on 'sleeping' PB and screen displays the login prompt (but no one will attempt unlock the machine)

If I initiate an ssh call (regardless if I use dns resolution or ip address) from A and in the meantime the PB will go to sleep and will not wake up.

That's how simple it is to crash a PB.

can anyone explain what is going on?

hdk

 

[Koodauw]

My powerbook doesnt have eternal sleep. (that I know of)

Is this a new feature on the latest revision?

 

[yellow]

100%?

Umm.. I cannot reproduce this.

AlPB, 10.4.3, wired or wireless. ssh waits everytime until the box is fully awake and then connects normally.

Are you trying to use a FQDN to ssh to, or a numerical IP?


Or is your step "let the PB fall back into eternal sleep" a step I'm misunderstanding? Are you just never logging into ssh and waiting for the PB to go to sleep again?

 

[spencecb]

What the hell is everyone talking about on this thread?

 

[yellow]

What the hell is everyone talking about on this thread?

hadek says you can 100% "crash" your PB with his above steps..

I refute that claim and await his/her return to clarify.

 

[spencecb]

hadek says you can 100% "crash" your PB with his above steps..

I refute that claim and await his/her return to clarify.

I understand what the original poster claims, as far as you can 100% crash your PB with his above steps...but I have no idea what is goin on in those steps.

 

[yellow]

Since I can get it to work (e.g. not crash/sleep) 100% of the time.. I wait for some renewed steps. I wonder if the user is having a DNS reverse lookup issue.

 

[hadek]

it's simple

By "eternal" I mean crash. My PB will not wake up.

What happens is this:
Two computers: A (any box) and PB.

If I open a lid on PB and screen displays the login screen (but no one will attempt unlock the machine)

If I initiate an ssh call (regardless if I use dns resolution or ip address) from A and in the meantime the PB will go to sleep and will not wake up.

That's how simple it is to crash a PB.

 

[TheMonarch]

Way to crash ANY Mac/OS X combo:


1) Transfer a file through network.
2) Disconnect server without warning during transfer.
3) Be mind boggled about how easily a network mishap can crash the best OS in the world.

 

[radiantm3]

Way to crash ANY Mac/OS X combo:


1) Transfer a file through network.
2) Disconnect server without warning during transfer.
3) Be mind boggled about how easily a network mishap can crash the best OS in the world.

That happened to me today.

 

[alexstein]

Way to crash ANY Mac/OS X combo:


1) Transfer a file through network.
2) Disconnect server without warning during transfer.
3) Be mind boggled about how easily a network mishap can crash the best OS in the world.

I noticed that before as well. It works everytime you want to crash your system.

 

[Benjamin]

Way to crash ANY Mac/OS X combo:

1) Transfer a file through network.
2) Disconnect server without warning during transfer.
3) Be mind boggled about how easily a network mishap can crash the best OS in the world.

Rumor also has it that dropping your mac into water during network transfer too will crash your mac.

 

[mbopy22]

I noticed that before as well. It works everytime you want to crash your system.

Why would anybody want to crash his/her computer????

If you want a computer that crashes offten... get a PC with XP and 256ram.. LOL

 

[grapes911]

Why would anybody want to crash his/her computer????

If you want a computer that crashes offten... get a PC with XP and 256ram.. LOL

I certainly want to know what crashes my computer. Then I know what to avoid doing. Like until now, I didn't know that "dropping your mac into water during network transfer too will crash your mac." Now I know and I'll try to stay away from water when using my PB when doing a network transfer.

 

[dollystereo]

Way to crash ANY Mac/OS X combo:


1) Transfer a file through network.
2) Disconnect server without warning during transfer.
3) Be mind boggled about how easily a network mishap can crash the best OS in the world.

I HATE THAT!!!
It happens every time I do transfers and my mom shuts down her powermac!!

 

[yellow]

That's how simple it is to crash a PB.

Aaaahhh... now I see what you're seeing. Sort of.. my PB comes back immediately from sleep if I hit the power button. But the ssh session hangs a lot.

Have you submitted this as a bug to Apple? You should.

http://www.apple.com/macosx/feedback/

 

[cube]

3) Be mind boggled about how easily a network mishap can crash the best OS in the world

The best consumer OS.

 

[ingenious]

The best consumer OS.

You mean the best OS.

 

[mkrishnan]

Hmmmm...now this network file transfer issue is making me paranoid. Even though I've personally never seen it.

Maybe it's a good thing that the WebDAV here doesn't work properly, and I have to use Goliath? Because the network drives go down altogether too frequently.

 

[alexstein]

Why would anybody want to crash his/her computer????

If you want a computer that crashes offten... get a PC with XP and 256ram.. LOL

Did you read this Thread's title: "100% certain way to crash any PB/OS...)

I just added a sarcastic reply to the thread. Lighten up! I know that nobody here "wants their computers to crash!".

But you can't change the fact that it happens once in awhile and it certainly can happen very very easy when the server or the host computer abruptly disconnects or shuts down during a wireless/wired network transfer.

 

[contoursvt]

Way to crash ANY Mac/OS X combo:


1) Transfer a file through network.
2) Disconnect server without warning during transfer.
3) Be mind boggled about how easily a network mishap can crash the best OS in the world.

You gotta be kidding me. I'm going to try it on my G3 10.2.x setup. Cant be that easy. LOL

 

[ingenious]

You gotta be kidding me. I'm going to try it on my G3 10.2.x setup. Cant be that easy. LOL

Yeah, really...

All that should do is beachball for at the max 30s and then OS X will say [Server Name] Connection Lost <Disconnect>. I don't think I've ever had OS X crash like that.