fixing FRED autostart @Ubuntu 16.04

Piotr Przybył piotr at
Fri Aug 19 15:36:17 CEST 2016

Hello everyone

I have some remarks about starting FRED components automatically after boot in Ubuntu 16.04 LTS
xenial. If anyone has some input, please share.

First, I suspect that upstart job definitions are obsolete and should removed. I mean the files:

Next, right after installation the services of FRED were not enabled, hence:

# cd /lib/systemd/system
# systemctl enable fred*

This is not enough, since fred-pyfred failed because it was started too early (before omniorb name
server), therefore I modified unit definition of fred-pyfred in
so now it looks like this:


ExecStart=/usr/sbin/fred-pyfred -d


and generates the following result:

# systemd-analyze critical-chain fred-pyfred.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

fred-pyfred.service @6.814s
└─omniorb4-nameserver.service @6.774s +23ms
  └─ @6.764s
    └─NetworkManager-wait-online.service @927ms +5.837s
      └─NetworkManager.service @665ms +185ms
        └─dbus.service @639ms
          └─ @639ms
            └─ @639ms
              └─snapd.socket @637ms +1ms
                └─ @634ms
                  └─ @634ms
@629ms +3ms

(of course your delays will vary).

To check if FRED services are running, one may use
# systemctl status fred*

Maybe this page could get an update?

Best regards
Piotr Przybył

More information about the fred-users mailing list