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

Explain why we manually publish state #351

Merged
merged 1 commit into from
Apr 19, 2014

Conversation

bcwaldon
Copy link
Contributor

No description provided.

@bcwaldon
Copy link
Contributor Author

I'd like to make go-systemd do the right thing, but this helps explain why we manually refresh state for now.

@@ -274,6 +274,10 @@ func (a *Agent) UnloadJob(jobName string) {

a.ForgetJob(jobName)
a.systemd.UnloadJob(jobName)

// The dbus event systemd will not trigger an event telling
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

really? why doesn't UnitRemoved get triggered?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

go-systemd isn't listening for UnitRemoved.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh nuts to go-systemd.

@jonboulle
Copy link
Contributor

:shipit:

@jonboulle
Copy link
Contributor

could you file an issue for follow up please?

@bcwaldon
Copy link
Contributor Author

Absolutely.

bcwaldon added a commit that referenced this pull request Apr 19, 2014
Explain why we manually publish state
@bcwaldon bcwaldon merged commit 19aaad2 into coreos:master Apr 19, 2014
@bcwaldon bcwaldon deleted the manual-refresh-state branch April 19, 2014 00:40
@bcwaldon
Copy link
Contributor Author

#352

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.

2 participants