I'm running a Pi as a server of SSH and SAMBA.
I have read various accounts about the Pi going to sleep. Some say their monitor sleeps, for some it's SSH. I'm running a Pi server with no desktop on it. My desktop PC puts nearly all its data onto the Pi server. However, as others have reported, the Pi has 20 second sleep periods. This means that SSH stops for this period. SAMBA also stops but, it appears to be at different times to SSH ( though I could be mistaken).
This is what I have found so far.
1. 'ping' localhost on the server does not keep the server awake, it still drops out on my desktop machine.
2. 'ping' xbmcIP (my media centre) from the server. This also does not help to keep communications up on my desktop machine.
3. 'ping' my desktop, or desktop ping server, keeps all communications alive and nippy on my desktop machine. Videos etc. play immediately with no problems. Applications needing to pick up files launch quickly. SSH doesn't drop out.
As a temporary measure I have the server pinging my desktop computer every second.
EDIT: Every 10 seconds seems to work OK. Every 15 seconds results in the initial connection being delayed.
So, it seems that it isn't the Pi server going to sleep but the communication to any IP that isn't constantly busy. It can't be just SSH where the problem lies because pinging server to desktop keeps SAMBA alive too.
So, has anyone any ideas, please, on what might be causing this problem?