Re: [systemd-devel] Proper way of installing avahi dbus activation file
El lun, 26-10-2015 a las 22:06 +0100, Reindl Harald escribió: > [...] > by the Also/Alias in the install section of proper units like the > Fedora > ones > > [root@srv-rhsoft:~]$ cat /usr/lib/systemd/system/avahi-daemon.service > [Unit] > Description=Avahi mDNS/DNS-SD Stack > Requires=avahi-daemon.socket > > [Service] > Type=dbus > BusName=org.freedesktop.Avahi > ExecStart=/usr/sbin/avahi-daemon -s > ExecReload=/usr/sbin/avahi-daemon -r > NotifyAccess=main > > [Install] > WantedBy=multi-user.target > Also=avahi-daemon.socket > Alias=dbus-org.freedesktop.Avahi.service Thanks a lot :) With this solution, what will occur if a user forgets to enable avahi always but I open gtk printing dialogs that will try to spawn avahi on demand? Will they be launched then or should we tell people to enable avahi-daemon always and have it running all the time? :/ Best regards ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Proper way of installing avahi dbus activation file
Hello In some distributions we are needing to run this: ln -s avahi-daemon.service /usr/lib/systemd/system/dbus -org.freedesktop.Avahi.service To get avahi started when needed, otherwise, logs will start to be logged about avahi being unable to be started when, for example, I try to print something. The problem is that reading: https://fedoraproject.org/wiki/Packaging:Systemd#DBus_activation "Note that the creation/removal of the alias symlinks should be done with "systemctl enable" and "systemctl disable" only. You should not create these symlinks manually" It's not clear how could upstream to ensure this link is installed :/ https://github.com/lathiat/avahi/issues/29 Thanks a lot for your help ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] build-sys: add configure option to disable LTO/gold
El jue, 19-02-2015 a las 00:48 +0100, Michael Biebl escribió: [...] > Incidentally, we do have to remove the -Wl,-fuse-ld=gold line in > Debian as well, since gold is problematic/less mature on various > architectures. > > > Couldn't we just add -Wl,-fuse-ld=gold via LDFLAGS in autogen.sh? > We also drop the gold and LTO usage on Gentoo for similar issues ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Readahead collect - root filesystem only?
El jue, 15-01-2015 a las 14:38 +0100, Reindl Harald escribió:
> Am 15.01.2015 um 14:33 schrieb Zbigniew Jędrzejewski-Szmek:
> > On Thu, Jan 15, 2015 at 02:31:22PM +0100, Reindl Harald wrote:
> >> Am 15.01.2015 um 14:40 schrieb Nikolai Zhubr:
> >>> 15.01.2015 16:07, Cristian Rodríguez:
> The readahead collector is no longer included in systemd.
> >>>
> >>> Hm. It is still there in not-very-old opensuse 13.2 ...
> >>> Anyway. Where has it gone then? Is it a separate tool now or got
> >>> obsoleted by something else?
> >>> I actually just started to like it... Quite a usefull thing...
> >>
> >> it was completly removed with no replacement by assuming eveorybody
> >> in a short term will use only SSD drives
> >>
> >> http://lists.freedesktop.org/archives/systemd-devel/2014-August/022002.html
> >
> > That's not the complete story. The other is that there were issues
> > with it, and nobody was working on them
>
> that's all fine
>
> but why the heck was there a need to include it in systemd, replace the
> all the years existing readahead daemon from Fedora and then abandon and
> remove it finally?
>
> that's one reason why so many people are annoyed be systemd take over
> more and more components far away from an init-daemon and if
> systemd-upstream later decides that part is no longer interesting and
> nobody has a need to use it like readahead what happens then?
>
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
I have been able to compile, install and run only the readahead part
from systemd-216 with newer systemd as I would still
want to run it (I don't have any SSD device and I still notice its
action when booting + login in my Gnome session... also I neither plan
to renew my main laptop or try to change its harddisk).
The problem is that I don't know how could I
make the systemd-readahead-done part to work as systemd-notify dropped
the readahead support:
http://cgit.freedesktop.org/systemd/systemd/diff/src/notify/notify.c?id=d6bc8348d5be8576a475ac8ced2b0146e60fb71f
Anyway, I got surprised by /.readahead looking to not grow more a bit
after booting (without "done" it should supposedly grow forever). One
workaround could be to call systemd-readahead-collect with the --timeout
option and hardcode there a value (a bit like e4rat behaves) but I am
not sure if something better could be done :/
From the old manpage I can see this info about "-done":
systemd-readahead-done.service is executed a short while after
boot completed and signals systemd-readahead-collect.service to end data
collection. On this signal, this service will then sort the
collected disk accesses and store information about them in /.readahead.
Reading the -collect .service file, looks like manually creating
a /run/systemd/readahead/done file should stop the service but I would
appreciate if anyone with more knowledge could confirm :|
The full drop commit is:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=d6bc8348d5be8576a475ac8ced2b0146e60fb71f
And looking to the readahead-collect.c part:
http://cgit.freedesktop.org/systemd/systemd/diff/src/readahead/readahead-collect.c?id=d6bc8348d5be8576a475ac8ced2b0146e60fb71f
Seems that playing with /run/systemd/readahead/{cancel,done,noreplay}
files should be enough, then, maybe I could create a shell wrapper to
mimic "systemd-notify --readahead" and use that to create the desired
files under /run/systemd/readahead.
Thanks a lot for your help
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] I wonder… why systemd provokes this amount of polarity and resistance
El mar, 28-10-2014 a las 17:05 +0100, Lennart Poettering escribió: [...] > http://lists.freedesktop.org/archives/systemd-devel/2014-October/024325.html Looks interesting. Have you think in having some kind of wiki or page listing this kind of "tricks" to solve things like that. That way we prevent people from applying many different solutions that could have different drawbacks and also have them in a place a bit more easily accessible Thanks a lot ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [HEADS-UP] Intent to remove readahead from systemd
El vie, 26-09-2014 a las 08:58 +0200, Tom Gundersen escribió: > On Thu, Sep 25, 2014 at 6:40 PM, Pacho Ramos wrote: > > El jue, 25-09-2014 a las 16:44 +0200, Tom Gundersen escribió: > >> On Thu, Aug 14, 2014 at 7:16 PM, Lennart Poettering > >> wrote: > >> > So, I think with the release after the upcoming one we should just > >> > remove it from the systemd package and just throw it on the pile of > >> > historic cruft. So, yeah, here's the advance warning that this will be > >> > happening... > >> > > >> > (Well, unless somebody from the community who cares and wants to invest > >> > the necessary time in it steps up and gives it the love it really > >> > needs. If nobody does until that release, I will delete the component > >> > from systemd). > >> > >> No one objected to this, so I pushed the patch deleting it. If anyone > >> wants to resurrect this in an external repo, it should be simple > >> enough to extract it from git. > >> > >> Cheers, > >> > >> Tom > >> ___ > >> systemd-devel mailing list > >> systemd-devel@lists.freedesktop.org > >> http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > > > Is there any other readahead implementation around that we could migrate > > to? Well, not sure many laptops with SSD are sold in your area but, at > > least in mine, most people still have (and buy) setups with rotational > > hard drives that have a clear gain when running readahead (well, I can > > see it every time I reboot and login on gnome-shell if I don't use > > readahead) > > I think the best bet would be someone who understands/knows/uses this > stuff to resurrect systemd-readahead in a third-party repo and > maintain it there. AFAIK, it was the best of the available options. > > Cheers, > > Tom Yeah, the problem was that I ended up using it as it looked to be the best option for doing this (even being "stalled"), the problem is that, even if I "use" it actively, I don't "understand/know" it :S Lets see if anyone finally is able to, at least, repackage it outside systemd (even simply keeping it, for now, as good (=> better than other alternatives) as it's currently) Best regards ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [HEADS-UP] Intent to remove readahead from systemd
El jue, 25-09-2014 a las 16:44 +0200, Tom Gundersen escribió: > On Thu, Aug 14, 2014 at 7:16 PM, Lennart Poettering > wrote: > > So, I think with the release after the upcoming one we should just > > remove it from the systemd package and just throw it on the pile of > > historic cruft. So, yeah, here's the advance warning that this will be > > happening... > > > > (Well, unless somebody from the community who cares and wants to invest > > the necessary time in it steps up and gives it the love it really > > needs. If nobody does until that release, I will delete the component > > from systemd). > > No one objected to this, so I pushed the patch deleting it. If anyone > wants to resurrect this in an external repo, it should be simple > enough to extract it from git. > > Cheers, > > Tom > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel Is there any other readahead implementation around that we could migrate to? Well, not sure many laptops with SSD are sold in your area but, at least in mine, most people still have (and buy) setups with rotational hard drives that have a clear gain when running readahead (well, I can see it every time I reboot and login on gnome-shell if I don't use readahead) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Regarding how to properly use zram on a systemd setup
Hello After reading: http://www.chromestory.com/2013/03/google-enabling-zram-for-chrome-os-by-default/ http://lwn.net/Articles/545244/ I was wondering what would be the best way to use zram on a setup running systemd. This is because I have found a lot of scripts, unit files... but I don't know what is the best approach (at least from an "upstream point of view"): http://mystilleef.blogspot.com.es/2011/10/enable-zram-in-fedora.html http://software.opensuse.org/package/systemd-zram-service https://aur.archlinux.org/packages/zramswap/ I found this thread: http://lists.freedesktop.org/archives/systemd-devel/2012-November/007444.html In that one Lennart suggest that maybe some action from util-linux maintainers could help but, after that message, I don't see anything newer (maybe we could report that suggestion to util-linux maintainers to other place... or maybe a better solution was found later :/) Thanks a lot for your help and suggestions ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
