Re: [systemd-devel] [PATCH] vconsole: properly set terminal UTF-8 mode
Am 17.02.2011 19:52, schrieb Andrey Borzenkov:
> As it stands now, dracut 008 in generic (not hostonly) mode explicitly
> disables UTF-8 because UNICODE is not set:
>
> modules.d/10i18n/console_init:
>
> set_keyboard() {
> local param
>
> [ "${UNICODE}" = 1 ] && param=-u || param=-a
> kbd_mode ${param}
> }
>
> The problem is, you do not know whether UNICODE is not set because
> system is configured for non-UNICODE or because we do not know yet.
You are right... UNICODE should default to 1 in dracut. Will change.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] vconsole: properly set terminal UTF-8 mode
Am 18.02.2011 09:13, schrieb Harald Hoyer:
> Am 17.02.2011 19:52, schrieb Andrey Borzenkov:
>> As it stands now, dracut 008 in generic (not hostonly) mode explicitly
>> disables UTF-8 because UNICODE is not set:
>>
>> modules.d/10i18n/console_init:
>>
>> set_keyboard() {
>> local param
>>
>> [ "${UNICODE}" = 1 ] && param=-u || param=-a
>> kbd_mode ${param}
>> }
>>
>> The problem is, you do not know whether UNICODE is not set because
>> system is configured for non-UNICODE or because we do not know yet.
>
> You are right... UNICODE should default to 1 in dracut. Will change.
changed to vconsole.font.unicode=1 alias UNICODE=1
and fixed the hostonly mode legacy configuration file parsing.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how disable fsck on swap+lvm
On Fri, 18.02.11 01:37, Miklos Vajna (vmik...@frugalware.org) wrote: > On Thu, Feb 17, 2011 at 07:07:26PM +0300, Alexey Shabalin > wrote: > > But i have not some rule with "vgchange -a y", and have lv-disk as "LV > > Status not available" > > Here is what we use at the moment: > > [Unit] > Description=LVM activation > DefaultDependencies=no > After=udev-settle.service > Before=local-fs.target > ConditionPathExists=/sbin/vgchange Please don't litter unit files with unnecssary ConditionPathExists= please. .service files should be installed along side their binaries and shipped in the same packages. So that if the .service file exists the binary exists too, and if the binary doesn't then the .servie file doesn't exist either. Otherwise looks good. And yupp, e should have that in upstream LVM. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd --test still tries to execute quite some actions and fails
Example as non-root [bor@n2 ~]$ systemd --system --unit=graphical.target --test > /tmp/foo systemd 17 running in system mode. (+PAM +LIBWRAP +AUDIT -SELINUX +SYSVINIT -LIBCRYPTSETUP; fedora) FATAL: Could not load /lib/modules/2.6.33.7-server-2mnb/modules.dep: No such file or directory /sbin/modprobe failed with error code 1. Failed to set hostname to : Operation not permitted Netlink failure for request 1: Operation not permitted Failed to configure loopback device: Operation not permitted /etc/mtab is not a symlink or not pointing to /proc/self/mounts. This is not supported anymore. Please make sure to replace this file by a symlink to avoid incorrect or misleading mount(8) output. Failed to enable ctrl-alt-del handling: Operation not permitted Failed to open /dev/tty0: Permission denied Failed to allocate manager object: No such file or directory example as root in chroot [iurt cooker] rootn2/home/bor$ systemd --system --unit=graphical.target --test > /tmp/foo Failed to mount /sys/fs/cgroup: No such file or directory well ... this makes --test rather useless. I definitely do not want it to mess with anything on live system. All it is expected to do is "Determine startup sequence, dump it and exit.", *not* trying to mount, modprobe, etc etc ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how disable fsck on swap+lvm
A little nitpick/question: On Fri, Feb 18, 2011 at 1:37 AM, Miklos Vajna wrote: > [Unit] > Description=LVM activation > DefaultDependencies=no > After=udev-settle.service > Before=local-fs.target Is the Before=local-fs.target really necessary? Any mounts that will reside on the lvm will already be Before=local-fs.target, and in the case where automounts are used instead, I guess we do not want to wait for lvm before local-fs.target becomes available? I have the same question about the different fsck services. They should clearly be Before=*.mount, but wouldn't it be better if they were not Before=local-fs.service? Cheers, Tom ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how disable fsck on swap+lvm
On Fri, Feb 18, 2011 at 2:02 PM, Tom Gundersen wrote: > A little nitpick/question: > > On Fri, Feb 18, 2011 at 1:37 AM, Miklos Vajna wrote: >> [Unit] >> Description=LVM activation >> DefaultDependencies=no >> After=udev-settle.service >> Before=local-fs.target > > Is the Before=local-fs.target really necessary? > > Any mounts that will reside on the lvm will already be > Before=local-fs.target, and in the case where automounts are used > instead, I guess we do not want to wait for lvm before local-fs.target > becomes available? > I think it makes sense. As long as no file system is using LVM (at least, no filesystem, activated by default) there is no point to wait for it. > I have the same question about the different fsck services. They > should clearly be Before=*.mount, but wouldn't it be better if they > were not Before=local-fs.service? > Makes sense for the same reason. local-fs should wait only for filesystems, activated by default; they should handle own dependencies themselves. As long as we re on theme ... How to express interdependency between different virtual devices? I.e. we have at least mdadm and device-mapper; mdadm is quite probably assembled incrementally so there is no clear checkpoint we can wait for; and LVM can use arrays managed by mdraid so it has to be started after it. How folks are handling it in different distributions? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd and sshd.socket/sshd@.service
On Tue, 2011-02-08 at 13:08 +0100, Lennart Poettering wrote: > On Tue, 08.02.11 14:49, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote: > > > > Oh, intreresting. It's in "failed" state. Can you check syslog/kmsg if > > > systemd generated any kind of log output when this happened? i.e. around > > > Mon, 07 Feb 2011 22:36:51 +0300. This should give us a hint on what > > > might be wrong. > > > > > > Lennart > > > > > > > /var/log/messages does not contain any info > > sshd log says: error: Could not load host > > key: /etc/ssh/ssh_host_ecdsa_key , but this not critical (sshd runs > > after systemctl stat sshd.socket) > > Hmm, can you try to reproduce this when booting with > systemd.log_level=debug and systemd.log_target=kmsg on the kernel > cmdline? Then, kmsg should definitely include a message on what is going > on. (and when we found it we probably should bump up the error level of > that msg) > > Lennart > Hm.. I'm upgrade systemd to current (18) and reboot. After that systemct start sshd@.service says that unit name not valid. Is this correct behaviour? -- Vasiliy G Tolstov Selfip.Ru ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd --test still tries to execute quite some actions and fails
On Fri, 18.02.11 13:42, Andrey Borzenkov (arvidj...@gmail.com) wrote:
> Example as non-root
>
> [bor@n2 ~]$ systemd --system --unit=graphical.target --test > /tmp/foo
> systemd 17 running in system mode. (+PAM +LIBWRAP +AUDIT -SELINUX
> +SYSVINIT -LIBCRYPTSETUP; fedora)
> FATAL: Could not load /lib/modules/2.6.33.7-server-2mnb/modules.dep:
> No such file or directory
> /sbin/modprobe failed with error code 1.
> Failed to set hostname to : Operation not permitted
> Netlink failure for request 1: Operation not permitted
> Failed to configure loopback device: Operation not permitted
> /etc/mtab is not a symlink or not pointing to /proc/self/mounts. This
> is not supported anymore. Please make sure to replace this file by a
> symlink to avoid incorrect or misleading mount(8) output.
> Failed to enable ctrl-alt-del handling: Operation not permitted
> Failed to open /dev/tty0: Permission denied
> Failed to allocate manager object: No such file or directory
The only real problem here is the last line, the rest is ignored. Could
you run this with --log-level=debug? This should give us an indication
why the last line failed. (And also give us an indication which log
message we should bump from "debug" to "info", so that the next one
running into this problem will see what's going on)
> example as root in chroot
>
> [iurt cooker] rootn2/home/bor$ systemd --system
> --unit=graphical.target --test > /tmp/foo
> Failed to mount /sys/fs/cgroup: No such file or directory
>
> well ... this makes --test rather useless. I definitely do not want it
> to mess with anything on live system. All it is expected to do is
> "Determine startup sequence, dump it and exit.", *not* trying to
> mount, modprobe, etc etc
Well, I didn't want to clutter the sources with too many "if
(!in_test_mode) { ... }", so I simply rely on the kernel refusing these
operations. And that does work properly, as you can see by the EPERMs
shown. The big issue you running into is in the last line where the
error isnt EPERM but ENOENT...
Lennart
--
Lennart Poettering - Red Hat, Inc.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd and sshd.socket/sshd@.service
On Fri, 18.02.11 14:27, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote: > > On Tue, 2011-02-08 at 13:08 +0100, Lennart Poettering wrote: > > On Tue, 08.02.11 14:49, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote: > > > > > > Oh, intreresting. It's in "failed" state. Can you check syslog/kmsg if > > > > systemd generated any kind of log output when this happened? i.e. around > > > > Mon, 07 Feb 2011 22:36:51 +0300. This should give us a hint on what > > > > might be wrong. > > > > > > > > Lennart > > > > > > > > > > /var/log/messages does not contain any info > > > sshd log says: error: Could not load host > > > key: /etc/ssh/ssh_host_ecdsa_key , but this not critical (sshd runs > > > after systemctl stat sshd.socket) > > > > Hmm, can you try to reproduce this when booting with > > systemd.log_level=debug and systemd.log_target=kmsg on the kernel > > cmdline? Then, kmsg should definitely include a message on what is going > > on. (and when we found it we probably should bump up the error level of > > that msg) > > > > Lennart > > > > Hm.. I'm upgrade systemd to current (18) and reboot. After that systemct > start sshd@.service says that unit name not valid. Is this correct > behaviour? Yes, it is. "sshd@.service" is merely a template name. You cannot start it just like that. It needs to be instantiated as "sshd@SOMETHING.service". You have the choice to either start "sshd.service", which is the traditional stand-alone ssh server. Or you instead start "sshd.socket", which uses inetd-style per-connection sshd instances. For that it will spawn one instance of sshd for each conection and those are going to be instances of "sshd@.service" with the socket address used as instance name, for example: "sshd@192.168.47.11-55-10.0.1.3-88.service". Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd --test still tries to execute quite some actions and fails
On Fri, Feb 18, 2011 at 2:29 PM, Lennart Poettering
wrote:
> On Fri, 18.02.11 13:42, Andrey Borzenkov (arvidj...@gmail.com) wrote:
>
>> Example as non-root
>>
>> [bor@n2 ~]$ systemd --system --unit=graphical.target --test > /tmp/foo
>> systemd 17 running in system mode. (+PAM +LIBWRAP +AUDIT -SELINUX
>> +SYSVINIT -LIBCRYPTSETUP; fedora)
>> FATAL: Could not load /lib/modules/2.6.33.7-server-2mnb/modules.dep:
>> No such file or directory
>> /sbin/modprobe failed with error code 1.
>> Failed to set hostname to : Operation not permitted
>> Netlink failure for request 1: Operation not permitted
>> Failed to configure loopback device: Operation not permitted
>> /etc/mtab is not a symlink or not pointing to /proc/self/mounts. This
>> is not supported anymore. Please make sure to replace this file by a
>> symlink to avoid incorrect or misleading mount(8) output.
>> Failed to enable ctrl-alt-del handling: Operation not permitted
>> Failed to open /dev/tty0: Permission denied
>> Failed to allocate manager object: No such file or directory
>
> The only real problem here is the last line, the rest is ignored.
No. The real problem is that it tries to do all of this. Fortunately
it is not permitted if running as non-root.
> Could
> you run this with --log-level=debug? This should give us an indication
> why the last line failed. (And also give us an indication which log
> message we should bump from "debug" to "info", so that the next one
> running into this problem will see what's going on)
>
[bor@n2 ~]$ systemd --system --unit=graphical.target --test --log-level=debug
systemd 17 running in system mode. (+PAM +LIBWRAP +AUDIT -SELINUX
+SYSVINIT -LIBCRYPTSETUP; fedora)
Your kernel apparently lacks built-in autofs4 support. Might be a good
idea to compile it in. We'll now try to work around this by calling
'/sbin/modprobe autofs4'...
Your kernel apparently lacks built-in ipv6 support. Might be a good
idea to compile it in. We'll now try to work around this by calling
'/sbin/modprobe ipv6'...
About to execute: /sbin/modprobe -qab -- autofs4 ipv6
Forked /sbin/modprobe as 4605
FATAL: Could not load /lib/modules/2.6.33.7-server-2mnb/modules.dep:
No such file or directory
/sbin/modprobe failed with error code 1.
Failed to set hostname to : Operation not permitted
Netlink failure for request 1: Operation not permitted
Failed to configure loopback device: Operation not permitted
/etc/mtab is not a symlink or not pointing to /proc/self/mounts. This
is not supported anymore. Please make sure to replace this file by a
symlink to avoid incorrect or misleading mount(8) output.
Looking for unit files in:
/etc/systemd/system
/lib/systemd/system
Looking for SysV init scripts in:
/etc/rc.d/init.d
Looking for SysV rcN.d links in:
/etc/rc.d
Failed to enable ctrl-alt-del handling: Operation not permitted
Failed to open /dev/tty0: Permission denied
Failed to allocate manager object: No such file or directory
[bor@n2 ~]$
>> example as root in chroot
>>
>> [iurt cooker] rootn2/home/bor$ systemd --system
>> --unit=graphical.target --test > /tmp/foo
>> Failed to mount /sys/fs/cgroup: No such file or directory
>>
>> well ... this makes --test rather useless. I definitely do not want it
>> to mess with anything on live system. All it is expected to do is
>> "Determine startup sequence, dump it and exit.", *not* trying to
>> mount, modprobe, etc etc
>
> Well, I didn't want to clutter the sources with too many "if
> (!in_test_mode) { ... }", so I simply rely on the kernel refusing these
> operations.
Well ... I naively thought that "computing dependency" is pretty much
self consistent operation that can be executed right away as soon as
we see --test option ...
> And that does work properly, as you can see by the EPERMs
> shown. The big issue you running into is in the last line where the
> error isnt EPERM but ENOENT...
>
> Lennart
>
> --
> Lennart Poettering - Red Hat, Inc.
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how disable fsck on swap+lvm
On Fri, 18.02.11 12:02, Tom Gundersen (t...@jklm.no) wrote: > > A little nitpick/question: > > On Fri, Feb 18, 2011 at 1:37 AM, Miklos Vajna wrote: > > [Unit] > > Description=LVM activation > > DefaultDependencies=no > > After=udev-settle.service > > Before=local-fs.target > > Is the Before=local-fs.target really necessary? > > Any mounts that will reside on the lvm will already be > Before=local-fs.target, and in the case where automounts are used > instead, I guess we do not want to wait for lvm before local-fs.target > becomes available? Well, maybe syncing it to local-fs is not necessary, but we probably want to sync it to basic.target at least. Mounts are not the only users of block devices, so a later service might want to use it and hence we should make sure that normal services (which are started after basic.target) can rely that LVM stuff is set up. Some database servers are able to use block devices directly, without any FS on them. > I have the same question about the different fsck services. They > should clearly be Before=*.mount, but wouldn't it be better if they > were not Before=local-fs.service? You have a point there. I have now relaxed this to base.target. (Just to avoid confusion by stuff like udisks and other disk daemon software, which we might not want to start at a time where the fsck is still going on). Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd --test still tries to execute quite some actions and fails
On Fri, 18.02.11 14:38, Andrey Borzenkov (arvidj...@gmail.com) wrote:
> >> Failed to allocate manager object: No such file or directory
> >
> > The only real problem here is the last line, the rest is ignored.
>
> No. The real problem is that it tries to do all of this. Fortunately
> it is not permitted if running as non-root.
Yupp, and we rely on that.
> Failed to allocate manager object: No such file or directory
> [bor@n2 ~]$
Hmm, my guess is that this has something to do with the lacking autofs4
support. Unfortunately the log messages don't give us a hint what is
going on. May I ask you to gdb through manager_new and check which of
the operations it does actually fails?
> > Well, I didn't want to clutter the sources with too many "if
> > (!in_test_mode) { ... }", so I simply rely on the kernel refusing these
> > operations.
>
> Well ... I naively thought that "computing dependency" is pretty much
> self consistent operation that can be executed right away as soon as
> we see --test option ...
It does substantially more. It also parses the other config files, which
I thought was a good thing and I use this myself for testing.
Lennart
--
Lennart Poettering - Red Hat, Inc.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how disable fsck on swap+lvm
On Fri, 18.02.11 14:24, Andrey Borzenkov (arvidj...@mail.ru) wrote: > > I have the same question about the different fsck services. They > > should clearly be Before=*.mount, but wouldn't it be better if they > > were not Before=local-fs.service? > > > > Makes sense for the same reason. local-fs should wait only for > filesystems, activated by default; they should handle own dependencies > themselves. > > As long as we re on theme ... > > How to express interdependency between different virtual devices? I.e. > we have at least mdadm and device-mapper; mdadm is quite probably > assembled incrementally so there is no clear checkpoint we can wait > for; and LVM can use arrays managed by mdraid so it has to be started > after it. How folks are handling it in different distributions? The way for now is to do things how they always have been done, i.e. just initialize one after the other with lots of wasted time in between. On Fedora we still use a shell script for that copied out of the old rc.sysinit. In the long run all these things need to become dynamic and actively watch for devices popping up. But this requires bigger changes in both LVM and MD and we'll have to see when LVM and MD actually catch up with this and make the change. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how disable fsck on swap+lvm
On Fri, Feb 18, 2011 at 12:39 PM, Lennart Poettering wrote: > Well, maybe syncing it to local-fs is not necessary, but we probably > want to sync it to basic.target at least. Mounts are not the only users > of block devices, so a later service might want to use it and hence we > should make sure that normal services (which are started after > basic.target) can rely that LVM stuff is set up. Some database servers > are able to use block devices directly, without any FS on them. > >> I have the same question about the different fsck services. They >> should clearly be Before=*.mount, but wouldn't it be better if they >> were not Before=local-fs.service? > > You have a point there. I have now relaxed this to base.target. (Just to > avoid confusion by stuff like udisks and other disk daemon software, > which we might not want to start at a time where the fsck is still going on). Regarding syncing things with base.target: I agree that this is a good idea for the time being, to avoid a flood of bugs. However, in the long term would it not be better to avoid syncing stuff (like udev-settle.service, lvm.service, etc.) with base.target? If services cannot deal with this then 1) they are buggy as they would not be able to deal with devices being plugged/appearing after boot, so they should be fixed 2) in the interim they should get After=lvm.service (or whatever they rely on) to make it work like before and also make it clear that they are buggy. My apologies for going a bit off-topic... Cheers, Tom PS Sorry to Lennart for sending twice, I forgot to cc the ML ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Making "noauto" and "automount" independent
Hi, I have the following usecase, that might be a common one (I'm not sure). In addition to my root partition I have two partitions that I use with "comment=systemd.automount" and this works well. However, I think it could be optimized, so I want to ask your opinion about the following (I'll prepare a patch if people agree it is a good idea). One partition (let's say /boot) is almost never used and it is tiny, so it should not be fsck'ed or mounted unless it is actually accessed (and this is how it works now, great!). The other partition (let's say /home) is always used, it is huge, and it is on a slow rotating disk. In other words, I want to use it with automount so that boot can continue as far as possible without the partition being available (which is how it works now). However, I would like to start fsck'ing it as soon as possible, rather than wait for the first access. This is not happening now. There is a very easy fix: make automount, and noauto independent. The way things work now, automount implies noauto, but there is no reason it needs to be like this. In other words, if /boot has options "noauto,comment=systemd.automount" it works the way it does now. If /home has options "comment=systemd.automount", without the "noauto", then the mount unit is pulled in by local-fs.target. I.e.: local-fs.target Wants/After boot.automount (like now) local-fs.target Wants/After home.automount (like now) and Wants home.mount (new) Thoughts? Tom ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] install systemd unit in cmake build system
Good morning. I'm read http://0pointer.de/public/systemd-man/daemon.html that contains autoconf pkg-config example to install systemd files. Can somebody write exaple to cmake build system that install system unit for daemon? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Making "noauto" and "automount" independent
On Fri, 18.02.11 14:45, Tom Gundersen (t...@jklm.no) wrote: > There is a very easy fix: make automount, and noauto independent. The > way things work now, automount implies noauto, but there is no reason > it needs to be like this. Yupp, we definitely should do this. In fact we initially thought of using autofs this way. However I never thought of making this available when using configuration in fstab, but you are definitely right we should do this. Added this to the TODO list. > In other words, if /boot has options > "noauto,comment=systemd.automount" it works the way it does now. If > /home has options "comment=systemd.automount", without the "noauto", > then the mount unit is pulled in by local-fs.target. Yupp, I am sold! > local-fs.target Wants/After boot.automount (like now) > local-fs.target Wants/After home.automount (like now) and Wants home.mount > (new) > > Thoughts? Love it. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] man: fixed typo in SyslogIdentifier=
--- man/systemd.exec.xml |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index e9576e1..1f79e1e 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -412,7 +412,7 @@ /dev/console. - SyslogIdentifer= + SyslogIdentifier= Sets the process name to prefix log lines sent to syslog or the kernel log buffer with. If not set -- 1.7.4.1 -- Mike Kazantsev // fraggod.net ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] cryptosetup units must have timeout
[root@localhost ~]# systemctl status cryptsetup@secrets.service cryptsetup@secrets.service - Cryptography Setup for secrets Loaded: loaded (/dev/.systemd/generator-ImgwKs/cryptsetup@secrets.service) Active: activating (start) since Mon, 21 Feb 2011 21:21:48 -0500; 11min ago Main PID: 670 (systemd-cryptse) CGroup: name=systemd:/system/cryptsetup@.service/secrets └ 670 /lib/systemd/systemd-cryptsetup attach secrets /de... [root@localhost ~]# date Mon Feb 21 21:33:23 EST 2011 Well, the problem is, these units are appeared to be stuck forever in activating state even if user never supplied password; and in this case the block shutdown for 3 minutes. Which is not good. May be they are constantly reactivated by respective mount unit. [root@localhost ~]# grep secrets /etc/fstab /etc/crypttab /etc/fstab:# secrets /etc/fstab:/dev/mapper/secrets /secrets ext2 defaults 2 2 /etc/crypttab:secrets UUID=9cb97898-8892-41fc-92d3-a655805addc3 none noauto Hmm ... no, mount unit is dead already [root@localhost ~]# systemctl status secrets.mount secrets.mount - /secrets Loaded: loaded Active: inactive (dead) Where: /secrets What: /dev/mapper/secrets CGroup: name=systemd:/system/secrets.mount and there are now pending password requests [root@localhost ~]# systemd-tty-ask-password-agent --list [root@localhost ~]# ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Inconsistent timeout properties name
In manual: JobTimeout RestartSec Timeout while in systemctl output they are JobTimeoutUSec RestartUSec TimeoutUSec ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
