Re: [systemd-devel] 2017: systemd-readahead?

[Che]

>
>
> However, I finally ditched it. I figured it will slow down boot of an
> aging system. Instead, I added bcache to my spinning rust plus an
> affordable SSD. This works very well and reduces boot times much better
> than readahead (by a factor of at least 5).


Perhaps such a feature is more useful as a diagnostic tool for
poorly-performing/broken systems.


-- grok.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] 2017: systemd-readahead?

[Che]

What's the 2017 status of systemd-readahead..? Permanently dead?


-- grok.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] wayland ..??!

[Che]

I'm wondering...

Has anyone yet invoked 'wayland' as being, in fact, a most diabolical
project... by which Lennart Poettering & Co. schemingly intend to take over
the GNUnix *graphics* universe, as well..?
:D
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Halt then reboot

[Che]

I wonder if it's possible to discuss matters, in any list, without
everything coming out looking like an insult and/or a put-down...
:/



On Sun, Sep 18, 2016 at 3:17 PM, Dark Penguin  wrote:

> Now that systemd manages the shutdown procedure, I don't know if it's
> possible to achieve the same behaviour (and thus make NUT work with
> systemd).
>

 As already mentioned, it is ouside of scope of OS actually. How you did
 it before systemd?

>>>
>>> It was actually a feature of NUT - and a default and recommended feature
>>> at some moment.
>>> See this, from their FAQ:
>>> http://networkupstools.org/docs/FAQ.html#_i_8217_m_facing_a_power_race
>>> And this - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835634
>>> (there is a link to an old discussion about implementing this feature).
>>> Now it doesn't work anymore, and I'm trying to find a new solution...
>>>
>>
>> So you do not even bother to describe how it worked before so others may
>> suggest how it can be (re-)implemented using systemd? Oh, well ...
>>
>
> No, that's not what I meant! Instead of trying to describe it myself, I've
> posted a link to their website where they describe the procedure
> first-hand! Basically, there is a "shutdown script" (though I'm not exactly
> sure where is it), which is apparently executed right before halting, so
> you can put "sleep" and "reboot" there. I was wondering if there is a
> similar thing in systemd.
>
>
> systemd supports switching back to initramfs instead of directly halting
 system. This allows you to implement your logic there after everything
 is completely shut down and unmounted (you probably need to unmount old
 root manually though). You can even monitor UPS from initramfs and only
 reboot when it reports power is back to make it safe.

>>>
>>> This may be the best idea without touching the kernel. But it still
>>> can't go through the "proper" halt procedure with syncing and unloading
>>> the drives, correct?..
>>>
>>
>> I have no idea what "unloading the drives" means.
>>
>
> That's why I've posted the second link: in that bug discussion, one person
> is explaining why this is a bad idea. In general, only the kernel can do
> "proper" halt, which among other things includes unloading the heads from
> the hard drive so that it is ready to be powered off (and apparently
> "hdparm -y" does not cut it somehow).
>
>
> --
> darkpenguin
>
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Flatpak 0.6.10 & systemd

[Che]

I don't know if URL links are acceptable on this list, but here's an
apropos one (since there is no separate user-only list):


Flatpak 0.6.10 Makes the Dependency on systemd in the User Session Optional:
http://news.softpedia.com/news/flatpak-0-6-10-makes-the-dependency-on-systemd-in-the-user-session-optional-508311.shtml
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Facility to debug/trace services especially at system startup time

[Che]

On Fri, Sep 9, 2016 at 11:17 PM, Pathangi Janardhanan 
wrote:

> Hi All,
>
>  What is the best option to do some debug/analysis of the system and the
> services started by systemd during initial bootup?
>
>  I would like to use tools like perf and strace etc. on some of the
> services. I could do this by starting the service manually but would like
> to have all the services that start at bootup and was wondering if there is
> a way for me to do this sort of thing, just for the initial boot up time.
>
> Thanks
> Jana
>

I believe there's some CLI, systemctl way to profile the sequence of events
by which various targets are reached. But some over-arching, powerful way
should exist, which is able to either: deconstruct the entire boot init
history; or to stop and trace the bootup process as it is occurring,
right..?

That would be very nice, eh? Perhaps there exists a present-moment hack
which is equivalent...
:)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] A question of sequential control of systemd service.

[Che]

On Tue, Aug 30, 2016 at 12:41 PM, Mantas Mikulėnas 
wrote:

> On Tue, Aug 30, 2016 at 6:31 PM, lin webber  wrote:
>
>>
>>
>> hello:
>> I have a question about systemd unit. I'm using ubuntu 16.04 whih
>> lightdm display manager . I have a service that I want to start it
>> completely before the lightdm service . it means that my service and
>> lightdm is not parallel started .  how can i write my unit file ,and what
>> to add in my service code ?
>>
>
> Use a Type= that lets systemd know when your service has 'started', e.g.
> Type=forking, Type=notify, or Type=dbus.
>
> e.g. for Type=notify make sure to call sd_notify(0, "READY=1") after
> startup.
>
> Then add "Before=lightdm.service" to [Unit].
>


I'll bet a lot of people would like to see a long series of simple
"'systemd 101' HOWTO" examples like this one. All conveniently listed in
some easy-to-browse places online.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd snapshot

[Che]

On Sat, Aug 20, 2016 at 11:53 PM, Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> On Sat, Aug 20, 2016 at 11:01:07PM -0400, Che wrote:
> > From GitHub:
> >
> > "Support for snapshots has been removed."
>
> See //github.com/systemd/systemd/commit/36b4a7ba55.
>
> Zbyszek
>

Well, that makes everything perfectly clear. Thanx.

And if in future, it becomes clear that was a premature move... well, then
it will be clear as to why.
:)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] systemd snapshot

[Che]

>From GitHub:

"Support for snapshots has been removed."

Has the back-story here been endlessly covered, here and elsewhere,
previously? And if so -- where would be the best place to read up on
understanding why it's no longer around in systemd..? Or perhaps someone
here will explain. Again, if necessary...
:)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Emulate two cron tab entries to start/stop service unit natively?

[Che]

On Fri, Aug 19, 2016 at 11:03 AM, Lennart Poettering  wrote:

... However, systemd
> does not support natively to stop services by timer, currently. This
> means for the "systemctl stop" part you always have to explicitly
> invoke it.


Does it make sense to implement this as a feature? And if so, is it
scheduled to be so?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Systemd Questions

[Che]

On Sun, Aug 14, 2016 at 8:34 AM, Reindl Harald 
wrote:

>
> Am 14.08.2016 um 14:29 schrieb Tom Browder:
>

> 3. If Debian 8 is running systemd for a service, why do I need an
>> entry for a service in init.d?
>>
>
> you don't


If I'm not mistaken, systemd is still referenced in /etc/init.d in Debian
in some way, because systemd is still de facto transitional: and thus
continues to maintain backward compatibility with SysVinit. So many people
will probably not understand why systemd continues to be linked to various
parts of the old SysVinit system -- when it is supposed to be outright
replacing it.

Point is: it takes time to properly and safely transition core
infrastructure.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Where is systemd non-devel list?

[Che]

On Fri, Jul 29, 2016 at 5:52 AM, Lennart Poettering 
wrote:

> On Thu, 28.07.16 17:52, Chip (jeffsch...@gmail.com) wrote:
>
> > I see that my question re: issues with systemd, is more suited for non
> > development list.
> >
> > Is there a non development systemd list?
>
> There is none for now. Just use the -devel list. As long as the noise
> doesn't get too bad we'd like to keep this together, as it ensures the
> user's questions don't end up in nirvana but in the focus of
> developers.
>

Exactly the question I had.

This should definitely be a question in the FAQ for this elist.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel