or a "compiled
version"(containing resolved dependencies, or even the boot up
sequence)
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Original Message-
>> From: systemd-devel [mailto:systemd-devel-
>> boun...@lists.freedesktop.org] On Behalf Of cee1
>> Sent: Wednesday, May 13, 2015 11:52 AM
>> To: systemd Mailing List
>> Subject: [systemd-devel] Reduce unit-loading time
>>
>> Hi a
2015-05-17 17:45 GMT+08:00 Martin Pitt :
> Hello cee,
>
> cee1 [2015-05-16 0:46 +0800]:
>> Thanks for the suggestion, it was other processes running in parallel
>> which presumably consuming lots of IO, after sending SIGSTOP at the
>> first (and SIGCONT later), the uni
:00 Martin Pitt :
> Hello cee1,
>
> cee1 [2015-05-18 18:24 +0800]:
>> Does the readahead-*.service shipped with systemd work for you?
>
> systemd dropped the builtin readahead in 217. It's reasonably easy to
> get back by reverting the "drop readahead" patche
manager_check_finished(), which is in turn invoked in
job_finish_and_invalidate() -- All these happens before the
manager_loop running.
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/m
25fa6901f72c300b5980ada0ef44c5
>
> Would be cool if you could check if this patch already fixes the issue
> for you.
It doesn't work :-(
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
to meet the dependencies,
and *** make the best schedule decision ***, e.g. If A is a much more
dependent unit, do not start A with too many units in parallel
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
htt
___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hey,
Just mention it, we've implemented similar fsck progress report in
LOonux3[1] several years ago.
FYI:
* http://lists.freedesktop.org/archive
2015-05-22 3:36 GMT+08:00 Lennart Poettering :
>
> Should be fixed in git. Please verify!
Confirmed, thanks!
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/s
2015-05-20 1:01 GMT+08:00 Martin Pitt :
> Hey cee1,
>
> cee1 [2015-05-18 23:52 +0800]:
>> At the first glance, I find ureadahead has some difference compared
>> with the readahead once in systemd, IIRC:
>
> Yes, for sure. systemd's was improved quite a bit. ureadahe
.
"""
unix 2 [ ACC ] SEQPACKET LISTENING 326 1/systemd
/run/udev/control
"""
Curious why?
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.fr
other device initialization stuffs.
2) Notifying systemd, let systemd start related daemons.
Is it right?
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
/acls/fix ownership create
> symlinks and so on.
That means ** all ** dev nodes are there when devtmpfs is mounted?
I thought devtmpfs makes a limited number of nodes for early boot-up.
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-dev
by generators?
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
mount
process exited, code=exited status=32
Jan 01 08:00:02 localhost systemd[1]: Failed to mount Debug File System.
"""
foo.service is a service with DefaultDependencies=no and Conflicts and
Before shutdown.target
So why the Debug File System is mounted multi-times here
2015-06-09 18:10 GMT+08:00 Lennart Poettering :
> On Thu, 04.06.15 23:41, cee1 (fykc...@gmail.com) wrote:
>> So why the Debug File System is mounted multi-times here? Any idea?
>
> Hmm, my suspicion is that the file system might actually already be
> mounted by the kernel the s
r
readahead against the snapshot will always read ahead of actual
requesting blocks.
BTW, systemd-bootchart has a option to chart entropy, how is the
entropy involved in boot up procedure?
---
1.
http://linux-kernel.vger.kernel.narkive.com/0FC8rduf/ioprio-se
Hi all,
Why we need to read/save random seed? Can it be read from /dev/random each time?
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
ed above 0, and as such, is currently the only HWRNG mixed into
> /dev/random by default."
>
>
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
2015-06-16 0:21 GMT+08:00 Lennart Poettering :
> On Mon, 15.06.15 23:33, cee1 (fykc...@gmail.com) wrote:
>
>> Hi,
>>
>> I maybe got confused.
>>
>> First, systemd-random-seed.service will save a "seed" from
>> /dev/urandom when shutdown, and l
2015-06-17 16:40 GMT+08:00 Reindl Harald :
>
> Am 17.06.2015 um 05:06 schrieb cee1:
>>
>> 2015-06-16 0:21 GMT+08:00 Lennart Poettering :
>>>
>>> On Mon, 15.06.15 23:33, cee1 (fykc...@gmail.com) wrote:
>>>>
>>>> Hi,
>>>>
>
2015-06-17 22:03 GMT+08:00 Lennart Poettering :
> On Wed, 17.06.15 20:21, cee1 (fykc...@gmail.com) wrote:
>>
>> What I means is:
>> 1. Load a saved seed to /dev/urandom.
>> 2. The service read /dev/random, which will block until kernel thinks
>> there's e
;d be willing to take a patch for such a change.
The type of this systemd-random-seed.service should be "notify", right?
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
2015-06-17 23:38 GMT+08:00 Reindl Harald :
>
>
> Am 17.06.2015 um 17:08 schrieb cee1:
>>
>> 2015-06-17 22:03 GMT+08:00 Lennart Poettering :
>>>
>>> On Wed, 17.06.15 20:21, cee1 (fykc...@gmail.com) wrote:
>>>>
>>>>
>>>> What
2015-06-14 21:17 GMT+08:00 cee1 :
> Hi all,
>
> I've recently got another chance to improve the boot-time of a
> systemd-based device. I'd like to share the experience here, and some
> thoughts and questions.
Two more articles about boot optimization:
* http://free
not save a new seed. May not be the
proper behavior?
2. The STATUS sent by the second and third sd_notify() are not shown
in "systemctl status systemd-random-seed.service", need some kind of
improvement.
Please comment and give suggestions :)
--
Regards,
- cee1
0001-random-seed-Save
random-seed-load.service
Both of the services use the same binary "systemd-random-seed" with
different argv[1]("load" vs "save")
Seems better than the patch v1, what do you think?
2015-06-19 21:34 GMT+08:00 cee1 :
> Hi all,
>
> As discussed at
> http://li
2015-06-19 15:34 GMT+08:00 Chaiken, Alison :
> cee1 writes:
>> 3.1 "consider disabling readahead collection in the shipped devices,
>> but leave readahead replay enabled."
>
>
> ceel, are you aware that readahead is deprecated in systemd and has not been
> inc
urther ports and
integrates some kernel libraries to libabc??
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
2015-06-15 0:43 GMT+08:00 Greg KH :
> On Sun, Jun 14, 2015 at 12:49:55PM -0300, Cristian Rodríguez wrote:
>>
>> El jun. 14, 2015 10:21, "cee1" escribió:
>> >
>> > Hi all,
>> >
>> > Why we need to read/save random seed? Can it be re
--
Regards,
- cee1
0001-basic-util.c-fopen_temporary-close-fd-if-failed.patch
Description: Binary data
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
n);
return 0;
}
}
"""
If A __returns__ a result to B, but B has already died (After sending
a "method call" message):
1. It will return ENXIO or ESRCH, right?
2. dispatch_wqueue(), bus_write_message
all of mount_one will
*NOT* be detected(since r == 1). Is this the expected behavior?
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hi all,
I notice in sd_bus_track_new, a callback can be specified, but when it
will be invoked?
It seems it will not be triggered when a name in track is removed.
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
here, e.g. We can try
to read 0 bytes when pollfd.revents != POLLIN.
The same with loop_write.
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
ssize_t loop_write(int fd, const void *buf,
size_t nbytes, bool do_poll) {
return n > 0 ? n : -errno;
}
+/*
if (pollfd.revents != POLLOUT)
return n &g
2013/9/12 Lennart Poettering :
> On Thu, 12.09.13 09:43, cee1 (fykc...@gmail.com) wrote:
>
>> What about the following patch? It simply do read/write again if poll
>> returns, and let read/write report error if something is wrong.
>
> I guess that patch makes sense, but co
Let read()/write() report any error/EOF.
---
src/shared/util.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/src/shared/util.c b/src/shared/util.c
index 2009553..3c08650 100644
--- a/src/shared/util.c
+++ b/src/shared/util.c
@@ -2186,8 +2186,10 @@ ssize_t loop_re
2013/9/26 Zbigniew Jędrzejewski-Szmek :
> On Sun, Sep 22, 2013 at 09:10:47PM +0800, cee1 wrote:
>> Let read()/write() report any error/EOF.
> This look OK, but can you provide a bit of motivation?
It's a re-sent patch, the original thread is at
http://lists.freedesktop.org/archi
boot-up).
It would be better if Systemd could timely report which units are
still starting.
E.g. we limit the max starting units meanwhile(which may improve boot
performance). When blocked, tell plymouth which units are started and
which units are still starting of the current batch.
Any ideas?
/maps, more:
https://github.com/cee1/systemd/commit/89d049507734746f6f1100218ca97cc829b05e0a
* Has anyone tried the crash shell? I added a custom sysrq which will
send SEGV to init, hence triggered the crash(). According to the log,
crash shell was called and exited immediately.
--
Regards,
-
在 2013年2月13日星期三，Lennart Poettering 写道：
> On Tue, 12.02.13 13:43, cee1 (fykc...@gmail.com ) wrote:
>
> > Hi all,
> >
> > systemd will call crash() if received fatal signals. It will produce a
> > core dump for analysis.
> > However, it seems signal handler
ystem/plymouth-quit.service
Then, how does it notify plymouth boot splash to quit?
Also I noticed prefdm.service has relations with plymouth-quit.service:
Conflicts=plymouth-quit.service
After=plymouth-quit.service
What does that mean?
--
Regards,
-
43 matches
Mail list logo
