Hi, There's a bug open in Debian about AICCU not starting when used with systemd (though it's most likely not that specifically). One of the last things in the bug log is:
| Actually, a concise problem statement would be a good thing to have, as | it seems completely lost in the bug report. Let me try to provide that... We now no longer have the problems in the original report with the boot hanging but we still don't have AICCU coming up reliably at boot. The problem seems to be that AICCU is started before the network is available (this is with the network managed via NetworkManager) and can't cope with that: Feb 17 12:19:11 slippershell aiccu[517]: Couldn't resolve host tic.sixxs.net, service 3874 Feb 17 12:19:11 slippershell aiccu[517]: Couldn't connect to the TIC server tic.sixxs.net Feb 17 12:19:11 slippershell aiccu[517]: Couldn't retrieve first tunnel for the above reason, aborting There's probably some init based fix for this but I'd also expect AICCU to handle this more gracefully by retrying resolver failures, it seems like this is something that is reasonably likely to happen during the startup process. Restarting after boot does seem to work perfectly happily, it's just the above issue. I'm guessing that this is what the ifup.d script that was there in earlier package versions was intended to fix. Thanks, Mark
signature.asc
Description: PGP signature
