If you don't have a DE you don't have a session manager either, so
systemd-logind can't help you anyway.
Indeed, you should just run your screenlocker.
--
Кирилл Елагин
On Sun, Jun 29, 2014 at 9:57 AM, Ivan Shapovalov intelfx...@gmail.com
wrote:
27 июня 2014 г., в 21:54, Lennart Poettering
...@gmail.com
// sent from phone
On Jun 29, 2014 1:02 PM, Kirill Elagin kirela...@gmail.com wrote:
If you don't have a DE you don't have a session manager either, so
systemd-logind can't help you anyway.
Indeed, you should just run your screenlocker.
--
Кирилл Елагин
On Sun, Jun 29, 2014 at 9:57
`systemctl reload-or-restart`?
--
Кирилл Елагин
On Sun, Jun 22, 2014 at 10:05 PM, Vasiliy Tolstov v.tols...@selfip.ru
wrote:
Hi. I have a problem - bird service.
[Unit]
Description=BIRD routing daemon ipv6 version
After=network.target
[Service]
ExecStart=/usr/bin/bird6 -f -u bird -g
Please, try to ssh into the system when it is stuck and show us the log
from `journalctl -b`.
Or, alternatively, do as earlier, reboot the stuck system, boot with
init=/bin/sh and get the log with `journalctl -b -1`.
But ssh is preferred as it will let you troubleshoot the issue further
I'm sorry to cut in but that's too interesting to keep just observing.
I guess it was `Failed to _g_et boot id` and it its about
`/proc/sys/kernel/random/boot_id`.
Is that kernel 2.3.15 or what?
{- offtopic
~~~
systemd-readahead[1486]: Failed to create fanotify object: Function not
implemented
On Fri, Jun 13, 2014 at 11:01 AM, Kirill Elagin kirela...@gmail.com wrote:
I guess it was `Failed to _g_et boot id` and it its about
`/proc/sys/kernel/random/boot_id`.
Is that kernel 2.3.15 or what?
Oh, never mind, that's probably just because `/proc` is not mounted when
`init=/bin/sh
No it's definitely not a blocker.
You forgot to attach a log your previous message.
--
Кирилл Елагин
On Fri, Jun 13, 2014 at 1:09 PM, Jay D Bhatt jay.bh...@igate.com wrote:
Hi Kirill,
I got to enable CONFIG_FANOTIFY in kernel, but I think this will not be
high priority or blocking
First of all the log is somewhat deformed. You could probably add
`--no-pager` or something like this to see the full lines.
It's not clear why mounting /tmp fails as I can't see any errors about
failing to mount /run and as far as I can tell there should be an error
logged in case it fails as
On Wed, Jun 11, 2014 at 3:24 AM, Mike Gilbert flop...@gentoo.org wrote:
On Tue, Jun 10, 2014 at 5:50 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 10.06.14 13:58, Mike Gilbert (flop...@gentoo.org) wrote:
Symlinks should probably just be considered different type of file,
.
Regards
Mohit Agrawal
- Original Message -
From: Kirill Elagin kirela...@gmail.com
To: Mohit Agrawal moagr...@redhat.com
Cc: systemd Mailing List systemd-devel@lists.freedesktop.org
Sent: Wednesday, June 4, 2014 1:03:47 PM
Subject: Re: [systemd-devel] How to Restrict device in systemd
, Jun 11, 2014 at 12:15 PM, Kirill Elagin kirela...@gmail.com
wrote:
On Wed, Jun 11, 2014 at 3:24 AM, Mike Gilbert flop...@gentoo.org
wrote:
On Tue, Jun 10, 2014 at 5:50 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 10.06.14 13:58, Mike Gilbert (flop...@gentoo.org) wrote
`failed` is a state of a unit and as such it is documented in `systemd` man
page.
I'm not sure if `systemd` man page fits into your definition of
“associated”.
Units may be active (meaning started,
bound, plugged in, ..., depending on the unit type, see below), or
First of all, according to docs, `DeviceAllow` syntax is somewhat different
from what you have.
Second, you might want to check `DevicePolicy`, as now your unit has access
not only to `/dev/zero`, but also to four other devices.
And hm, I thought, those directives control access to device nodes.
DevicePolicy=strict
ExecStart=/usr/bin/dd if=/dev/zero of=/root/file_1 bs=1M count=400
Restart=always
[Install]
WantedBy=multi-user.target
I believe it should restrict to create the file .
Regards
Mohit Agrawal
- Original Message -
From: Kirill Elagin kirela...@gmail.com
To: Mohit
at 11:29 AM, Kirill Elagin kirela...@gmail.com wrote:
Well, first of all, your `DeviceAllow` syntax is still wrong. “Takes two
space-separated strings: a device node path (such as /dev/null) followed by
a combination of r, w, m”.
But that's not the main issue here. The main issue here
Might be that rfkill1 disappears after rfkill0 is switched off, if they are
related.
--
Кирилл Елагин
On Wed, May 28, 2014 at 8:43 AM, Mantas Mikulėnas graw...@gmail.com wrote:
On May 28, 2014 3:25 AM, Aaron Lewis the.warl0ck.1...@gmail.com wrote:
Hi,
I'm running Arch and recently
The container usecase alone is already the reason why I am so very sure
I want this stuff, and that it needs to be in networkd, and just work. I
want this fully automatic, so that we can create a hundred of veth
tunnels, and trivially easy (simply by setting DHCPServer=yes for their
.network
Deja vu ;).
http://lists.freedesktop.org/archives/systemd-devel/2014-May/019136.html
So, yes, wrapper seems to be the way to go.
--
Кирилл Елагин
On Wed, May 21, 2014 at 10:18 PM, Vasiliy Tolstov v.tols...@selfip.ruwrote:
2014-05-21 21:49 GMT+04:00 Ran Benita ran...@gmail.com:
Oops, I
Could it be that all the boot ids are actually the same for some reason?
I had this issue in a container when systemd was reading boot_id from
`/proc/sys/kernel/random/boot_id` and since /proc was bind-mounted, boot_id
always was host's boot_id.
You can also run `journalctl -F _BOOT_ID` to see a
OK, I've just re-read your message and it looks like all you need is add
`PIDFile` to your unit.
systemd will behave as expected: once your main process terminates it will
re-read PID
from this file (assuming that before dying your old process writes its
child's PID) and
set it as MAINPID for your
I've just tested the way I described it and everything worked perfectly.
Definitely the issue is this short period of time, I'm almost sure
(didn't check the source, though) that systemd re-reads pidfile
the moment the main process terminates.
What's wrong with writing the new pid from the old
That's how you do this in systemd:
http://pkgs.fedoraproject.org/cgit/couchdb.git/tree/couchdb.tmpfiles.conf
https://projects.archlinux.org/svntogit/community.git/tree/trunk/couchdb.tmpfiles?h=packages/couchdb
--
Кирилл Елагин
On Sat, May 3, 2014 at 12:03 PM, Austin Matherne
On Apr 30, 2014 12:23 PM, Tom Gundersen t...@jklm.no wrote:
On 30 Apr 2014 09:21, Florian Weimer fwei...@redhat.com wrote:
I don't know if we can change /dev/urandom to block because that
doesn't look very backwards-compatible to me.
I have seen Ted Ts'o write about wanting this, but I
While playing with this I've also noticed that systemd treats symlinks in a
bit
weird way: looks like if it sees a symlink it dereferences it, but not all
the symlinks
in the path. Here is an example:
# systemctl show systemd-udevd.service -p FragmentPath
Yeah, I see this with systemd 212.
And let me clarify a little bit: this delay after showing first 10 lines is
not a result of looking up for something;
Following lines appear as soon as there is something new in the log (that
is, actually what `-f` does).
So, here is what I see:
I type
arg_lines to 10, we still get just 10 lines of
output. And then the rest.
--
Кирилл Елагин
On Wed, Apr 23, 2014 at 9:53 PM, Kirill Elagin kirela...@gmail.com wrote:
Yeah, I see this with systemd 212.
And let me clarify a little bit: this delay after showing first 10 lines
is not a result
On Wed, Apr 23, 2014 at 10:16 PM, Lennart Poettering lenn...@poettering.net
wrote:
What actually happens is that the output will show you everything from
today, and when it is done with that continue with a live output.
Not exactly. You don't get _everything_ form to day, you get just
The description of repo on GitHub says “Mirror of git://
anongit.freedesktop.org/systemd/systemd”.
That is, it's a mirror. I don't know how exactly it is synchronised, but,
since it is a mirror,
it might be out of date sometimes.
--
Кирилл Елагин
On Tue, Apr 8, 2014 at 10:52 AM, Kevin Wilson
Hi,
There are plenty people who have some kind of automatic session unlocking
set up.
Examples are: BT phone proximity, USB-drive being plugged in, etc.
This is normally done via DBus `ScreenSaver.SetActive(false)` call, but
this interface is not
well-documented and, actually, it seems that this
On Thu, Apr 3, 2014 at 11:51 PM, Leonid Isaev lis...@umail.iu.edu wrote:
On a battery-powered system, they are most likely clean due to small
uptime.
I can't agree.
Nowadays battery-powered systems tend to have huge uptimes
due to being mostly suspended and rarely powered-off/rebooted.
30 matches
Mail list logo
