On 11.08.2007, at 04:39, Frank Edwards wrote:

> I think this may be related to use of nohup and/or the rc process
> environment. I've altered interfaces.inc to include the hostapd -B  
> flag (run
> as a daemon process), and included changes to start/stop hostapd  
> the same
> way as  racoon in vpn.inc.

Ah, that's a good clue, thanks - I'll try to figure out what exactly  
it is that hostapd doesn't like about the environment during boot.

> Suggested fix...

Unfortunately that will fail if WPA is used on more than one wireless  
interface (hostapd can't write its PID to a file after forking,  
unlike most other daemons), which is why I chose the nohup solution.

- Manuel