[Bug 176472] Re: netatalk fails to start on boot when "roaming mode" enabled

[Tommy Trussell]

I apologize for the lack of updates but I quit using Netatalk when I
"retired" most of my oldest Macintosh hardware running Mac OS 9 and
Ubuntu 6.06 on the PowerPC hardware and Ubuntu 7.10 on the Intel
hardware. Nowadays I've updated the Intel hardware to 12.04 LTS and
abandoned the PowerPC. I appreciate the feedback from tsanga but at this
point I don't recall whether I tested his workaround.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/176472

Title:
  netatalk fails to start on boot when "roaming mode" enabled

Status in sysvinit:
  Invalid
Status in “netatalk” package in Ubuntu:
  Incomplete
Status in “upstart” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: netatalk

  I've been running Netatalk on a system since it was running Dapper
  6.06 or Edgy 6.10. Now I'm running Gutsy 7.10 and noticed Netatalk
  doesn't start at boot, though it starts readily when invoked manually
  using

  sudo /etc/init.d/netatalk start

  There are no messages logged anywhere regarding the failed start so
  it's hard to know where to look for the problem. I honestly don't
  remember if it started correctly under Ubuntu Feisty 7.06. There are
  no error messages when it's started manually -- just a "normal" entry
  in /var/log/messages saying papd CUPS support is enabled.

  I found a forum discussion about it --
  http://ubuntuforums.org/showthread.php?t=486949

  Based on this discussion I looked at the system-V and upstart scripts,
  and the scripts seem to be where they should be. I also tried removing
  the bootsplash and netatalk still does not start on boot. I have not
  tried any changes to my /etc/hosts or network configuration.

  I see several bugs where people had trouble installing netatalk, such
  as Bug #109917, Bug #158076, Bug #157685 and Bug #159202 -- all of
  these seem to be difficulties with the network interface. That may be
  the problem here -- maybe the interface is not ready when Netatalk
  starts, HOWEVER why does it not log anything at all -- not even the
  attempt to start?

  Could there be something odd about the netatalk code that doesn't play
  well with upstart?

  P.S.: I AM using netatalk "insecurely" on my LAN since I have not
  recompiled the package to use ssh as reported in Bug #26452 -- my file
  sharing clients connect using cleartext passwords.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sysvinit/+bug/176472/+subscriptions