<div dir="ltr"><div>I thought I would move this discussion to a new thread.<br><br></div><div>I looked after a proposal to disable the autopilot with snappy config but I did not find such a mail.<br><br></div><div>Meanwhile, I experimented more with the commands on the page that Leo proposed.<br><a href="https://github.com/ubuntu-core/snappy/blob/master/docs/autopilot.md">https://github.com/ubuntu-core/snappy/blob/master/docs/autopilot.md</a><br><br></div><div>When I say:<br>systemctl disable snappy-autopilot.timer<br></div><div>it does remove the autopilot symlink from the /etc/systemd/system/multi-user.target.wants directory.<br><br></div><div>Before:<br>root@localhost:/etc/systemd/system/multi-user.target.wants# ls<br>cgmanager.service         rsyslog.service                                       <br>cgproxy.service           snappy-autopilot.timer                                <br>cloud-config.service      ssh.service                                           <br>cloud-final.service       ubuntu-snappy.boot-ok.service                         <br>cloud-init-local.service  ubuntu-snappy.firstboot.service                       <br>cloud-init.service        ubuntu-snappy.grub-migrate.service                    <br>cron.service              ubuntu-snappy.run-hooks.service                       <br>pppd-dns.service          webdm_snappyd_0.9.4.service                           <br>remote-fs.target          <br><br></div><div>After:<br>root@localhost:/etc/systemd/system/multi-user.target.wants# ls<br>cgmanager.service         remote-fs.target<br>cgproxy.service           rsyslog.service                                       <br>cloud-config.service      ssh.service                                           <br>cloud-final.service       ubuntu-snappy.boot-ok.service                         <br>cloud-init-local.service  ubuntu-snappy.firstboot.service                       <br>cloud-init.service        ubuntu-snappy.grub-migrate.service                    <br>cron.service              ubuntu-snappy.run-hooks.service                       <br>pppd-dns.service          webdm_snappyd_0.9.4.service     <br><br></div><div>However, reboot somehow recreates the link.<br></div><div>After reboot:<br>root@localhost:/etc/systemd/system/multi-user.target.wants# ls                  <br>cgmanager.service         rsyslog.service                                       <br>cgproxy.service           snappy-autopilot.timer                                <br>cloud-config.service      ssh.service                                           <br>cloud-final.service       ubuntu-snappy.boot-ok.service                         <br>cloud-init-local.service  ubuntu-snappy.firstboot.service                       <br>cloud-init.service        ubuntu-snappy.grub-migrate.service                    <br>cron.service              ubuntu-snappy.run-hooks.service                       <br>pppd-dns.service          webdm_snappyd_0.9.4.service                           <br>remote-fs.target    <br><br></div><div>Can this be the BeagleBone's SD card filesystem?<br><br></div><div>Regards,<br></div><div>Gabor<br></div><div><br></div>John Lenton wrote:<br>so, first off, if you're seeing that message then autopilot is still enabled.<br>
<br>
However, doing the stop (and especially the disable) means it's going<br>
to be disabled at the next boot. Maybe after doing this you played<br>
with “<span class="">snappy</span> <span class="">config</span>”? I remember telling you about using <span class="">snappy</span> <span class="">config</span><br>
to enable/disable this, so that could be it. Anyway, if <span class="">snappy</span> <span class="">config</span><br>
doesn't effectively disable it, it's a bug, please let us know (with<br>
steps-to-reproduce, given I've just tried to reproduce what you<br>
described and got nowhere).<br></div>