Re: [systemd-devel] Github issue progress stalled

[Philip Müller]

On 08.12.2015 11:57, Colin Guthrie wrote:
> 
> There also seems to be no way to remove a "needs-reporter-feedback" tag
> after I've provided feedback so it'll probably be getting ignored in any
> workflows you use that exclude bugs with that tag.
> 
> How is this workflow with GH issues supposed to work?
> 
> Col
> 

Hi Colin,

since you're the reporter and you already gave some information as
feedback Lennart has to decide if this was helpful enough for him what
you have posted so far.

However I can still see that your "quest" is still open:

Try connecting with gdb to PID 1 and see which event causes it to wakeup
all the time. for that set a breakpoint on source_dispatch and look at
s->description which hopefully contains a short string that tells you
which source is being triggered there ...

greez
Phil
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Where is DHCP Address stored?

[Philip Müller]

Am 28.11.2015 um 17:00 schrieb Tom Gundersen:
> On Sat, Nov 28, 2015 at 4:42 PM, J Decker  wrote:
>> On Sat, Nov 28, 2015 at 7:36 AM, Tom Gundersen  wrote:
>> Arch; did an update lastnight/this morning when my networking fell apart.
> 
> As far as I can tell the fixes for these issues are upstream, but not
> backported. You could try with current git, or ask downstream to
> backport.
> 

Well, I see in this regard followed commit: resolved: fix typo in
in_addr_is_localhost()

https://github.com/systemd/systemd/commit/db15affc05be7ba8d2089e655e653b59458d9c6f

Or is something else still needed to fix this?



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

Re: [systemd-devel] Where is DHCP Address stored?

[Philip Müller]

Am 28.11.2015 um 17:00 schrieb Tom Gundersen:
>> Arch; did an update lastnight/this morning when my networking fell apart.
> As far as I can tell the fixes for these issues are upstream, but not
> backported. You could try with current git, or ask downstream to
> backport.
> 

Ok, seems these might be needed to fix this:

https://github.com/systemd/systemd/pull/2029
https://github.com/systemd/systemd/commit/ff7d5a5c7c9faa553a24861db4bf531560df9c0d
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] terminals not appearing

[Philip Müller]

Am 18.08.2015 um 20:24 schrieb Michał Zegan:
 Hello.
 
 I have the newest arch, systemd version 224.
 
 The thing that I wonder about is that sometimes, when I press
 ctrl+alt+f1..f6, ttys do not appear and I do not see the login prompt.
 Like there is an initial tty1, but when I start a gui, it is freed.
 Other ttys often just do not appear.

Sometimes the wiki helps here:

https://wiki.archlinux.org/index.php/Systemd_FAQ#How_do_I_change_the_default_number_of_gettys.3F

greez
Phil

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

Re: [systemd-devel] [ANNOUNCE] systemd 200

[Philip Müller]

Maybe you guys send me a patch I should test ...
Atm I can reproduce it on every build on my i686 installation.
I can confirm that 64bit using the same packages doesn't produce this error.

Am 05.04.2013 23:33, schrieb Zbigniew Jędrzejewski-Szmek:

On Fri, Apr 05, 2013 at 11:26:49PM +0200, Zbigniew Jędrzejewski-Szmek wrote:

On Fri, Apr 05, 2013 at 07:32:53PM +0200, Lennart Poettering wrote:

On Sat, 30.03.13 18:41, Philip Müller (ph...@manjaro.org) wrote:


Same issue with make check as reported before:


http://lists.freedesktop.org/archives/systemd-devel/2013-March/009971.html

Hmm, this looks really weird. I cannot reproduce this here, and valgrind
shows nothing. I wonder if this has to do something 32bit vs. 64bit (I
only have the latter here).

Can anyone reproduce the issue when running test-bus-marshal through
valgrind on x86-32?

Hi,

I had a go at debugging this... I think that the is the return of the
va_arg and undefined aps horror. The result is that in test-bus-marshall.c:133
and test-bus-marshall.c:139 (at least), some of the output arguments are not
initialized at all and segfault happens. Under gdb I see that va_arg(ap, void*)
returns y twice.

According to va_arg(3), If ap is passed to a function that uses
va_arg(ap,type) then the value of ap is undefined after the return of
that function. So message_read_ap calling itself recursively is not an
option.

...unless we implement DBUS_FORMAT_FORMAT_ADVANCE, which calls itself
recursively (yuck), and use va_copy (yuck). But maybe that's the way.

Zbyszek


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

Re: [systemd-devel] [ANNOUNCE] systemd 200

[Philip Müller]

Same issue with make check as reported before:

http://lists.freedesktop.org/archives/systemd-devel/2013-March/009971.html

Am 29.03.2013 04:14, schrieb Lennart Poettering:

Heya,

System Five Hundred has now reached Version Two Hundred, how awesome is
that?

Mostly bug fixes.

http://www.freedesktop.org/software/systemd/systemd-200.tar.xz

CHANGES WITH 200:

 * The boot-time readahead implementation for rotating media
   will now read the read-ahead data in multiple passes which
   consist of all read requests made in equidistant time
   intervals. This means instead of strictly reading read-ahead
   data in its physical order on disk we now try to find a
   middle ground between physical and access time order.

 * /etc/os-release files gained a new BUILD_ID= field for usage
   on operating systems that provide continuous builds of OS
   images.

 Contributions from: Auke Kok, Eelco Dolstra, Kay Sievers,
 Lennart Poettering, Lukas Nykryn, Martin Pitt, Václav Pavlín
 William Douglas, Zbigniew Jędrzejewski-Szmek

Lennart

PS: To get the above bit about System Five Hundred, think about the
roman numeral for 500... (and while you are at it, I hope you figured out
the relation to System V, now ;-))



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

Re: [systemd-devel] [ANNOUNCE] systemd 199

[Philip Müller]

Here on this machine it still fails. It can also be an issue with this 
installation.

I created a tarball out of git with followed commit as last one:

590888a0d0cb813714fa2a521e2ca711f75862fb 
http://cgit.freedesktop.org/systemd/systemd/commit/?id=590888a0d0cb813714fa2a521e2ca711f75862fb


Still the same result:

PASS: test-bus-signature
./build-aux/test-driver: Zeile 95: 20079 Speicherzugriffsfehler 
(Speicherabzug geschrieben) $@  $log_file 21

FAIL: test-bus-marshal

Will test it on a different machine now.

Am 27.03.2013 06:07, schrieb William Giokas:

On Tue, Mar 26, 2013 at 05:40:59PM +0100, Philip Müller wrote:

systemd-199 build just fine on 64bit, but on 32bit it fails during check:

PASS: test-sleep
./build-aux/test-driver: line 95: 18318 Segmentation fault (core
dumped) $@  $log_file 21

Fixed as of 49e5de64e22ea4794092b91393545ab08e658e0a for me.



___
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

Re: [systemd-devel] [ANNOUNCE] systemd 199

[Philip Müller]

systemd-199 build just fine on 64bit, but on 32bit it fails during check:

PASS: test-sleep
./build-aux/test-driver: line 95: 18318 Segmentation fault (core dumped) 
$@  $log_file 21


Full check-log is attached.

Linux manjaro 3.4.37-1-MANJARO #1 SMP PREEMPT Wed Mar 20 22:08:42 CET 
2013 i686 GNU/Linux

glibc 2.17-3, gcc 4.7.2-4, make 3.82-5

kind regards

Phil

Am 26.03.2013 17:12, schrieb Lennart Poettering:

Heya,

Many bugfixes but a few new features, too.

http://www.freedesktop.org/software/systemd/systemd-199.tar.xz

(Note that the git tag is still missing in the repo. Currently there's
something wrong with the git tag verifier in the repo on fdo, so I can't
push this... I will push the tag as soon as that is fixed. v199 is
commit efc0ac6af6a105e38d1b0a37d8d5d016c76713cc)

== Starting check()...
make: Entering directory `/home/phil/dev/git/basis/systemd/src/systemd-199'
make --no-print-directory check-recursive
Making check in .
make --no-print-directory  test/sys
  GEN  test/sys
make --no-print-directory check-TESTS
PASS: test-env-replace
PASS: test/udev-test.pl
PASS: test-strbuf
PASS: test-strv
PASS: test-strxcpyx
PASS: test/rules-test.sh
PASS: test-util
PASS: test-job-type
PASS: test-unit-name
PASS: test-unit-file
PASS: test-replace-var
PASS: test-calendarspec
PASS: test-date
PASS: test-strip-tab-ansi
PASS: test-cgroup-util
PASS: test-sleep
./build-aux/test-driver: line 95: 18318 Segmentation fault  (core dumped) 
$@  $log_file 21
FAIL: test-bus-marshal
PASS: test-bus-signature
PASS: test-id128
PASS: src/udev/keymap/check-keymaps.sh
PASS: test-prioq
PASS: test-sched-prio
PASS: test-journal
PASS: test-journal-syslog
PASS: test-journal-match
PASS: test-journal-stream
PASS: test-journal-verify
PASS: test-mmap-cache
PASS: test-bus-chat
PASS: test-journal-send
make --no-print-directory all-recursive
Making all in .
Making all in po
make[7]: Nothing to be done for `all'.

Testsuite summary for systemd 199

# TOTAL: 30
# PASS:  29
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to http://bugs.freedesktop.org/enter_bug.cgi?product=systemd

make[4]: *** [test-suite.log] Error 1
make[4]: *** Deleting file `test-suite.log'
make[3]: *** [check-TESTS] Error 2
make[2]: *** [check-am] Error 2
make[1]: *** [check-recursive] Error 1
make: *** [check] Error 2
make: Leaving directory `/home/phil/dev/git/basis/systemd/src/systemd-199'
== ERROR: A failure occurred in check().
Aborting...

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

Re: [systemd-devel] [ANNOUNCE] systemd 199

[Philip Müller]

Attached the bus-marshal.log, if it helps.

Phil
message size = 362, contents =
6c010001ea0067126a0001016f0001002f0003017300040050696570020173000c00666f6f6261722e77616c646f060173000c00666f6f6261722e77616c646f080167001473617373617373617b79767d62612873732961730008006120737472696e671e000900737472696e67202331000900737472696e67202331000600666f6f62617228000300666f6f000300666f6f000300666f6f000300666f6f000300666f6f000300666f6f001c00030173000300666f6f00030173000300666f6f0001002e0003006161610001003100030061616100010031000300616161000100310016000600666f6f626172050077616c646f00
Type:method-call
Flags:   none
Version: 0
Serial:  4711
Headers:
  path - objectpath '/'
  interface - 'foobar.waldo'
  member - 'Piep'
  destination - 'foobar.waldo'
  signature - signature 'sassassa{yv}ba(ss)as'
Body: ('a string', ['string #1', 'string #1'], 'foobar', ['foo', 'foo', 'foo', 
'foo', 'foo'], 'foo', {byte 0x03: 'foo', 0x03: 'foo'}, true, [('aaa', '1'), 
('aaa', '1'), ('aaa', '1')], ['foobar', 'waldo'])
UNIX File Descriptors:
  (none)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [ANNOUNCE] systemd 199

[Philip Müller]

Hi,

I just tried to revert Zbigniew's patches and build it again. Still got 
the same error message:


2013-02-07 	tests: skip tests if manager cannot be created 
http://cgit.freedesktop.org/systemd/systemd/commit/src/test/test-unit-name.c?id=c5e33bf8342daa6bab22f495ef774741184de09d 
	Zbigniew Je;drzejewski-Szmek 	1 	-2/+8
2013-02-06 	tests: run manager in session mode 
http://cgit.freedesktop.org/systemd/systemd/commit/src/test/test-unit-name.c?id=fa3cd7394c227ad38c5c09b2bc2d035e7fb14a76 
	Zbigniew Je;drzejewski-Szmek 	1 	-4/+8
2013-01-30 	tests: add test for unit name printing 
http://cgit.freedesktop.org/systemd/systemd/commit/src/test/test-unit-name.c?id=1682ff60114b7a57972a03aa99f9864064593f72 
	Zbigniew Je;drzejewski-Szmek 	1 	-2/+90



On my x86_64 architecture using the same packages it builds just fine. I 
ran now gdb and created a backtrace.


Hope this helps.

Phil

Am 26.03.2013 19:10, schrieb William Giokas:

It ened by blaming this commit:

   [2a2473d89e02ccd923abc6e74cddd07798679a15] boot: add stub Makefile symlink
   1682ff60114b7a57972a03aa99f9864064593f72 is the first bad commit
   commit 1682ff60114b7a57972a03aa99f9864064593f72
   Author: Zbigniew Je;drzejewski-Szmekzbys...@in.waw.pl
   Date:   Tue Jan 29 15:25:36 2013 -0500

   tests: add test for unit name printing

   :100644 100644 c44ca0b76d53f8151e669ec4f8fa8dbf385ecba5
f0149310330408ced1e5e212bc5ef3684e3395da M  Makefile.am
   :04 04 389f403c2b93728e572bbc45f52803d5ed50225f
8d6a4318a1637cf7cc2f19605ca54f669891eef7 M  src


[phil@manjaro systemd-199]$ gdb test-bus-marshal
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i686-pc-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from 
/home/phil/dev/git/basis/systemd/src/systemd-199/test-bus-marshal...done.
(gdb) run
Starting program: 
/home/phil/dev/git/basis/systemd/src/systemd-199/test-bus-marshal 
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need set solib-search-path or set sysroot?
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3400.3-gdb.py, 
line 9, in module
from gobject import register
  File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module
import gdb.backtrace
ImportError: No module named backtrace
[Thread debugging using libthread_db enabled]
Using host libthread_db library /usr/lib/libthread_db.so.1.
Message 0x8056008
n_ref=1
endian=l
type=1
flags=0
version=1
serial=4711
fields_size=106
body_size=234
path=/
interface=foobar.waldo
member=Piep
destination=foobar.waldo
sender=n/a
signature=sassassa{yv}ba(ss)as
reply_serial=0
error.name=n/a
error.message=n/a
sealed=yes
BEGIN_MESSAGE sassassa{yv}ba(ss)as {
STRING: a string
BEGIN_ARRAY s {
STRING: string #1
STRING: string #1
} END_ARRAY 
STRING: foobar
BEGIN_ARRAY s {
STRING: foo
STRING: foo
STRING: foo
STRING: foo
STRING: foo
} END_ARRAY 
STRING: foo
BEGIN_ARRAY {yv} {
BEGIN_DICT_ENTRY yv {
BYTE: 3
BEGIN_VARIANT s {
STRING: foo
} END_VARIANT
} END_DICT_ENTRY
BEGIN_DICT_ENTRY yv {
BYTE: 3
BEGIN_VARIANT s {
STRING: foo
} END_VARIANT
} END_DICT_ENTRY
} END_ARRAY 
BOOLEAN: yes
BEGIN_ARRAY (ss) {
BEGIN_STRUCT ss {
STRING: aaa
STRING: 1
} END_STRUCT
BEGIN_STRUCT ss {
STRING: aaa
STRING: 1
} END_STRUCT
BEGIN_STRUCT ss {
STRING: aaa
STRING: 1
} END_STRUCT
} END_ARRAY 
BEGIN_ARRAY s {
STRING: foobar
STRING: waldo
} END_ARRAY 
} END_MESSAGE
message size = 362, contents =

Re: [systemd-devel] Hybrid-sleep needs to be executed bu superuser

[Philip Müller]

I think *Mantas Mikule.nas* fixed it some minutes ago:/

http://lists.freedesktop.org/archives/systemd-devel/2012-December/007766.html
/
Am 17.12.2012 21:33, schrieb Christian Hesse:

Federico Di Pierro nierr...@gmail.com on Mon, 2012/12/17 21:19:

Hi!
I'm using systemd 196 on my archlinux, with linux 3.7.0 .
I found out that systemctl hybrid-sleep needs to be ran as root. While my
session is active (using systemd-logind feature), and in fact i can
hibernate/poweroff/suspend with my normal user. But hybrid-sleep still
requires superuser privileges.
Is there any reason?
Thanks for your time!

I suppose this is just polkit missing the correct rules. Take a look
at /usr/share/polkit-1/actions/org.freedesktop.login1.policy and add the
block needed. I will take a look tomorrow if you did not success till then.


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

Re: [systemd-devel] [script] Eject CD before shutdown

[Philip Müller]

Yes it is the root-disk. I managed it by overwritting all messages with 
attached script.
No issues at all. It displays my message and reacts as wanted. No 
hangups etc.


Am 14.09.2012 19:20, schrieb Lennart Poettering:

On Fri, 14.09.12 00:14, Philip Müller (ph...@manjaro.org) wrote:


So, seems to work. I attached my current scripts and two picutes
with error messages.
Also I added now *read -t 30* and fixed hanging by pressing the
Enter-key. Is there any way
to hide those error messages (seems the system still tries to read
from CD after it got ejected),
so my message gets displayed clean? Maybe there is a way to get it cleaner.

You are ejecting the root disk? Well, that's difficult to get right.

You could transition back into an initrd of some kind and print the
message there:

http://www.freedesktop.org/wiki/Software/systemd/InitrdInterface

Or you could print this message from a script in
/usr/lib/systemd/system-shutdown and hope for the best. (And turn off
console printk output via /proc/sys/kernel/printk first). Since the
systemd-shutdown binary (which runs at the very end) locks itself into
memory you might be able to get away with that. That said, the initrd
thing is the only fix that would really get this right.

Lennart



#!/bin/sh

if [ -n $(blkid -L %MISO_LABEL% |grep -Eo 'sr|cd|loop') ]; then
cdrecord -eject

echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e  : 
echo -e

Re: [systemd-devel] [script] Eject CD before shutdown

[Philip Müller]

Since my distro is based on Archlinux I might go for the initrd-way.
Currently I'm testing the shutdown-script way ...

Am 15.09.2012 10:24, schrieb Philip Müller:
Yes it is the root-disk. I managed it by overwritting all messages 
with attached script.
No issues at all. It displays my message and reacts as wanted. No 
hangups etc.


Am 14.09.2012 19:20, schrieb Lennart Poettering:

On Fri, 14.09.12 00:14, Philip Müller (ph...@manjaro.org) wrote:


So, seems to work. I attached my current scripts and two picutes
with error messages.
Also I added now *read -t 30* and fixed hanging by pressing the
Enter-key. Is there any way
to hide those error messages (seems the system still tries to read
from CD after it got ejected),
so my message gets displayed clean? Maybe there is a way to get it 
cleaner.

You are ejecting the root disk? Well, that's difficult to get right.

You could transition back into an initrd of some kind and print the
message there:

http://www.freedesktop.org/wiki/Software/systemd/InitrdInterface

Or you could print this message from a script in
/usr/lib/systemd/system-shutdown and hope for the best. (And turn off
console printk output via /proc/sys/kernel/printk first). Since the
systemd-shutdown binary (which runs at the very end) locks itself into
memory you might be able to get away with that. That said, the initrd
thing is the only fix that would really get this right.

Lennart





___
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