Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

fix(systemd): Use LinkUnitFiles rather than EnableUnitFiles #414

Merged
merged 1 commit into from
May 7, 2014

Conversation

bcwaldon
Copy link
Contributor

@bcwaldon bcwaldon commented May 7, 2014

No description provided.

@bcwaldon
Copy link
Contributor Author

bcwaldon commented May 7, 2014

/cc @polvi @jonboulle

@polvi
Copy link
Contributor

polvi commented May 7, 2014

why not just drop this all together? What is it doing?

@bcwaldon
Copy link
Contributor Author

bcwaldon commented May 7, 2014

@polvi LinkUnitFiles offloads the work of linking our units from /run/fleet/units into the systemd search path, ignoring the [Install] section.

@bcwaldon
Copy link
Contributor Author

bcwaldon commented May 7, 2014

lgtm

bcwaldon added a commit that referenced this pull request May 7, 2014
fix(systemd): Use LinkUnitFiles rather than EnableUnitFiles
@bcwaldon bcwaldon merged commit e5280fc into coreos:master May 7, 2014
@bcwaldon bcwaldon deleted the quit-enabling branch May 7, 2014 20:07
@polvi
Copy link
Contributor

polvi commented May 7, 2014

lgtm fwiw!

Link a unit file that is not in the unit file search paths into the unit file search path. This requires an absolute path to a unit file. The effect of this can be undone with disable. The effect of this command is that a unit file is available for start and other commands although it is not installed directly in the unit search path.

@jonboulle
Copy link
Contributor

I'm hella confused, thought this was done already

ship eeeeet

@bcwaldon
Copy link
Contributor Author

bcwaldon commented May 7, 2014

@jonboulle I had updated go-systemd, but hadnt gotten as far as replacing the call to EnableUnitFiles.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants