ulėnas
> // sent from phone
> On Jun 29, 2014 1:02 PM, "Kirill Elagin" 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.
>&g
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
wrote:
> >> 27 июня 2014 г., в 21:54, Lennart Poettering
> написал(а):
> >
`systemctl reload-or-restart`?
--
Кирилл Елагин
On Sun, Jun 22, 2014 at 10:05 PM, Vasiliy Tolstov
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 bird
> ExecRelo
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
interactiv
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 /ru
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 wrote:
> Hi Kirill,
>
>
>
> I got to enable CONFIG_FANOTIFY in kernel, but I think this will not be
> high priority or blocking thing. Is it bloc
On Fri, Jun 13, 2014 at 11:01 AM, Kirill Elagin 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 mounte
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
You're welcome.
Please, tell the PMS guys to add this to the spec and ask the Paludis guys
to implement this as well.
--
Кирилл Елагин
On Thu, Jun 12, 2014 at 1:33 AM, Mike Gilbert wrote:
> On Wed, Jun 11, 2014 at 4:56 PM, Mike Gilbert wrote:
> > On Wed, Jun 11, 2014 at 12
t; Regards
> Mohit Agrawal
>
> - Original Message -
> From: "Kirill Elagin"
> To: "Mohit Agrawal"
> Cc: "systemd Mailing List"
> Sent: Wednesday, June 4, 2014 1:03:47 PM
> Subject: Re: [systemd-devel] How to Restrict device in systemd?
&
On Wed, Jun 11, 2014 at 3:24 AM, Mike Gilbert wrote:
> On Tue, Jun 10, 2014 at 5:50 PM, Lennart Poettering
> wrote:
> > On Tue, 10.06.14 13:58, Mike Gilbert (flop...@gentoo.org) wrote:
> >
> >> > Symlinks should probably just be considered different type of file,
> that
> >> > have a contents an
`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
"
агин
On Wed, Jun 4, 2014 at 11:29 AM, Kirill Elagin 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 th
f access that are explicitly
>specified.
>
> [Unit]
> Description=mydevblock
> [Service]
> DeviceAllow=/dev/zero
> DevicePolicy=strict
> ExecStart=/usr/bin/dd if=/dev/zero of=/root/file_1 bs=1M count=400
> Restart=always
> [Install]
> WantedBy=mul
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. W
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 wrote:
> On May 28, 2014 3:25 AM, "Aaron Lewis" wrote:
> >
> > Hi,
> >
> > I'm running Arch and recently upgraded system, now every time I b
>
> 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
> .ne
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 wrote:
> 2014-05-21 21:49 GMT+04:00 Ran Benita :
> > Oops, I thought you meant a condition. I do
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 s
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 pro
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
Have you looked into using sd_notify to update MAINPID?
--
Кирилл Елагин
On Mon, May 5, 2014 at 1:19 AM, Gerd v. Egidy wrote:
> Hi,
>
> I'm one of the developers of the Icinga monitoring system. We want to
> provide
> a .service file for our monitoring daemon with the next major release
> (Ic
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
wrote:
> I switche
On Apr 30, 2014 12:23 PM, "Tom Gundersen" wrote:
>
>
> On 30 Apr 2014 09:21, "Florian Weimer" 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 don't know much
more. Al
On Wed, Apr 23, 2014 at 10:16 PM, Lennart Poettering 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 arg_lines
lines.
And you ge
llow` sets 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 wrote:
> Yeah, I see this with systemd 212.
>
> And let me clarify a little bit: this delay after showing first 10 lines
> is not
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 `journalc
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
FragmentPath=/usr/lib64/systemd/system/sys
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 w
On Thu, Apr 3, 2014 at 11:51 PM, Leonid Isaev 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.
Anyway, I think Tomasz
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 c
31 matches
Mail list logo
