[systemd-devel] systemd remote active and systemd-journal-gateway
I was trying to centralize logging with systemd using the systemd-gateway and systemd-remote (active connect), But i have observed that when the transfer is complete, next time systemd-remote is run, it seems to start afresh from the start of the journal on the remote machine, is there a way for systemd-remote and gateway to pick up from the last position? Also it seems systemd-journal-upload and systemd-remote (passive listen) may be able to do this since journal-upload can safe cursor position, but i met a bug that fills my disk, when i used it with 4 nodes, but it seemed in testing with one remote host. Anyone know of a work around for this? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Two services allocated for the same bus name ...
I’m trying to set up two different Avahi configurations, using foo.service and bar.service. Error message: Two services allocated for the same bus name org.freedesktop.Avahi, refusing operation. On the face of it, that seems to be correct: indeed foo.service and bar.service both declare [Service] Type=dbus BusName=org.freedesktop.Avahi However, I have in foo.service: [Unit] Conflicts=bar.service and vice versa, so they will never be active at the same time. Is there some way to make this work? [I don’t know who might want to talk to Avahi via dbus, but it makes sense that they should find either foo or bar, depending on which configuration is currently up, so I don’t really want to rename this] Cheers, Johannes. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Two services allocated for the same bus name ...
11.10.2015 06:09, Johannes Ernst пишет: I’m trying to set up two different Avahi configurations, using foo.service and bar.service. Error message: Two services allocated for the same bus name org.freedesktop.Avahi, refusing operation. On the face of it, that seems to be correct: indeed foo.service and bar.service both declare [Service] Type=dbus BusName=org.freedesktop.Avahi However, I have in foo.service: [Unit] Conflicts=bar.service and vice versa, so they will never be active at the same time. Is there some way to make this work? [I don’t know who might want to talk to Avahi via dbus, but it makes sense that they should find either foo or bar, depending on which configuration is currently up, so I don’t really want to rename this] It sounds like you try to start both of them at the same time, is it correct? Cheers, Johannes. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] propagate reload from other events
I understand that if foo.service specifies: PropagatesReloadTo=bar.service and I execute “systemctl reload foo”, this will trigger a reload of bar as well. Typically I might do that if I have changed some config file, and I want the daemon(s) to pick it up. Is there a similar mechanism that triggers a reload in bar when foo stops, or when foo starts, or events like that? I found a thread from 3 years ago on an OnStop= rule, but I don’t think that made it into the mainline? [1] My use case is that if I switch from foo.service to foo2.service (both require bar, and are mutually exclusive to each other), I’d like bar to reload. [1] http://lists.freedesktop.org/archives/systemd-devel/2012-November/007304.html Thanks for the help, as always, Johannes. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
