Hi, On Wed, Nov 23, 2016 at 01:39:13PM +0100, MI wrote: > Package: tftpd-hpa > Version: 5.2+20140608-3 > > On Debian Jessie, the tftpd-hpa server is started (by systemd) before the > filesystems are mounted. > > There is no systemd unit file in the tftpd-hpa package, so the > /etc/init.d/tftpd-hpa script is used. However, the "INIT INFO" section in > the script seems to be ignored: > > ### BEGIN INIT INFO > # Provides: tftpd-hpa > # Required-Start: $local_fs $remote_fs $syslog $network > ... > > The log: > > $ journalctl -u tftpd-hpa > -- Reboot -- > Nov 22 08:02:34 r530a systemd[1]: Starting LSB: HPA's tftp server... > Nov 22 08:02:36 r530a tftpd-hpa[1396]: Starting HPA's tftpd: > in.tftpd/docs/pxe missing, aborting. > Nov 22 08:02:40 r530a systemd[1]: tftpd-hpa.service: control process > exited, code=exited status=1 > Nov 22 08:02:40 r530a systemd[1]: Failed to start LSB: HPA's tftp server. > Nov 22 08:02:40 r530a systemd[1]: Unit tftpd-hpa.service entered failed > state. > > I'm not sure if this could actually be considered a systemd bug, but anyway, > it is probably more efficient to just add a systemd unit file to the > package? Or maybe there is some other way to make sure that tftpd is started > when everything it needs is available?
That seems wrong ... aiui, the init scripts are supposedly run after all other units - so I'm going to guess you're doing something 'funny' and/or wrong with where and/or how you're mounting the tftp root you want to use ... I think you're going to need to tell us a bit more about that before we can know what's really going on here. Cheers, Ron
