up@.service that VDSM
could depend on? [Requires=, After=, etc.]
If not, could you write one (e.g. vdsm-ifup) and *then* make VDSM depend on
it?
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Accidentally dropped in 1aff20687f4868575.
---
rules/60-persistent-storage.rules | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rules/60-persistent-storage.rules
b/rules/60-persistent-storage.rules
index df490b0..d701b14 100644
--- a/rules/60-persistent-storage.rules
+++ b/ru
These are handled by a different driver than MemoryStick Pro.
---
rules/60-persistent-storage.rules | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/rules/60-persistent-storage.rules
b/rules/60-persistent-storage.rules
index d701b14..ade24dd 100644
--- a/rules/60-persiste
as*.)
So the number is mostly meaningless if you're trying to determine actual
resource usage. The "RSS" column in `ps u 1`, `pmap -x -p 1` or in htop
describes it a bit better. Generally systemd-pid1 will be ~5 MB; journald
tends to be the largest – it's 12 MB on
x27; shows no one is holding file open. However, the
> system does not reboot!
I *think* systemd closes the watchdog device cleanly when you disable it
via config, so the hardware timeout is no longer 'active'. Would be quite
surprising to the user, if it didn't.
Try suspending
On Tue, Mar 17, 2015 at 11:50 PM, Kay Sievers wrote:
> On Tue, Mar 17, 2015 at 5:00 PM, Mantas Mikulėnas
> wrote:
> > Accidentally dropped in 1aff20687f4868575.
> > ---
> > rules/60-persistent-storage.rules | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-
ts.freedesktop.org/mailman/options/systemd-devel>, log in with
email+password, change "Set Digest Mode" to "Off", click "Submit changes".
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Mar 27, 2015 23:03, "Smith, Kenneth"
wrote:
>
> I am trying to start a service that requires using a library that has the
same name as a preexisting one (it is a patched version). It is located in
a different path so that if I want to start it at the command line I can do
this:
>
> LD_LIBRARY_P
; > +if (errno != EAGAIN)
> > +log_error_errno(errno, "failed to expire automount:
> > %m");
>
> Please uppercase the first word of the message.
>
> Also, given that we don't actually do anything about the failure, i
> think we shoul
On Fri, Apr 3, 2015, 14:17 Lennart Poettering
wrote:
On Thu, 02.04.15 11:49, Al Lau (laua...@gmail.com) wrote:
> As a test, the "/usr/sbin/smartd $smartd_opts" is invoked from the command
> line and the daemon is forked and stayed up as expected. By default, the
> /usr/sbin/smartd daemonize.
eah, and if dbus isn't running, systemctl spews out this:
Error getting authority: Error initializing authority: Could not connect:
> No such file or directory (g-io-error-quark, 1)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-d
On Sat, Apr 4, 2015 at 7:37 AM, Andrei Borzenkov
wrote:
> В Fri, 3 Apr 2015 21:19:24 +0300
> Mantas Mikulėnas пишет:
>
> > Previously udev used to undo mounts when a device *disappeared;* when
> > systemd took over the task, it started unmounting things as soon as it
> &
On Sat, Apr 4, 2015 at 1:44 PM, Andrei Borzenkov
wrote:
> В Sat, 4 Apr 2015 12:55:34 +0300
> Mantas Mikulėnas пишет:
>
> > On Sat, Apr 4, 2015 at 7:37 AM, Andrei Borzenkov
> > wrote:
> >
> > > В Fri, 3 Apr 2015 21:19:24 +0300
> > > Mantas Mikulėnas
p is shared, software owned by various
users often has private subdirectories under it (which other uids cannot
access), and gnome-settings-daemon is just being unnecessarily verbose
about that.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
get doesn't wait
for *anything;
*it needs the provider-specific services to also be enabled, like
NetworkManager-wait-online.service (similarly for systemd-networkd and
ifupdown).
--
Mantas Mikulėnas
___
systemd-devel mailing list
syste
to do the cleanup as an unprivileged user actually interferes
> with systemd-tmpfiles (see df99a9ef5bb7a89b92 and
> https://bugzilla.redhat.com/show_bug.cgi?id=1183684).
>
Even a stat()? Ouch.
--
Mantas Mikulėnas
___
systemd-devel mailing l
2015 +0100
udevd: event - make db loading lazy in REMOVE event handling
But udev_node_remove() needs the DB to know about symlinks, so…
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
).
>
> I am not aware of any nicer way.
>
I think /proc//status in current linux.git has additional fields for
the process PIDs in all namespaces, so you could probably get the "outer"
PID by looking at the container's /proc.
--
Mantas Mikulėnas
On Thu, Apr 23, 2015 at 6:25 PM
>> Apr 24 04:48:45 server systemd-nspawn[496]: nginx: [emerg] open()
>> "/dev/stderr" failed (6: No such device or address)
>
> Any idea what the precise syscall is that triggers that? i.e. what
> strace says?
It kind of makes sense when stdout
On Fri, Apr 24, 2015 at 4:53 PM, Lennart Poettering
wrote:
> On Fri, 24.04.15 16:51, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
>> On Fri, Apr 24, 2015 at 4:24 PM, Lennart Poettering
>> wrote:
>> > On Fri, 24.04.15 12:06, Peter Paule (systemd-de...@fedu
On Apr 27, 2015 16:39, "Lennart Poettering" wrote:
>
> On Sun, 26.04.15 14:32, Peter Paule (systemd-de...@fedux.org) wrote:
>
> > BTW: I did the `echo "asdf" > /dev/stderr`-thing just to test if
> > `/dev/stderr` worked as expected.
>
> /dev/stderr does not work for socket fds, and that's a kernel
BIOS is up-to-date".
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
error_log logs/error.log error;
> Context: main, http, stream, server, location
>
Hmm, but that already lists a native config keyword for "stderr"?
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
lly like the idea of littering regular systems with even more
tangled mount namespaces, but still curious if this could work.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Tue, Apr 28, 2015 at 1:39 PM, Lennart Poettering
wrote:
> On Tue, 28.04.15 13:17, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
> > > Moreover, when this is set up
> > > the mount propagation from the user's namespace to the rest of system
> > > must be
xec/exit), of
course; but it's not the kernel's job to care about what is a 'daemon'
nor what daemons should be started & when.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
omp.sysutils.systemd.devel/21419
http://article.gmane.org/gmane.comp.sysutils.systemd.devel/21997
"Introducing sd_notify() messages that can notify PID 1 about daemons
reloading or shutting down, has been on the TODO list for a while"
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
e the user session
startup to user@, it's not going to help much, as it won't affect
console logins, SSH logins, and so on.
Instead, you should check if someone has written a PAM 'session'
module which could do this. (There's one for mount namespaces.) I
t;pid,
> ps->ppid, ps->total);
> --
> 1.9.3
If the name is not printable, wouldn't it be better to show it in
escaped form rather than pretend it doesn't exist at all?
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
er init systems like sysvinit and upstart) ?
Which glibc call exactly are you referring to?
reboot() tells the kernel to shut down (or reboot) immediately – it
doesn't call init, and it doesn't even as much as sync disks.
shutdown() has nothing to do with system power state; it closes
r words, you're unnecessarily reinventing the wheel and the
gearbox and everything else, *and* doing it poorly at that. The whole
point of an init system is to handle these things for you...
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-
to' option, then the generator
also symlinks the corresponding .mount unit under .device.wants/
(e.g. dev-sda3.device.wants/mnt-backup.mount), causing the .mount unit to
be triggered *every* time that device appears on the system.
That is, in addition to local-fs.target triggering foo.mount and w
utton)
logind[388]: New session c1 of user gdm.
logind[388]: Lid closed.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Thu, Aug 28, 2014 at 4:35 PM, Koen Kooi wrote:
>
>
> Op 28 aug. 2014, om 11:06 heeft Mantas Mikulėnas het
> volgende geschreven:
>
> > On Thu, Aug 28, 2014 at 11:50 AM, Koen Kooi
> > wrote:
> >>
> >> Hi,
> >>
> >> I am
ot;Apache Web Server" in its httpd.service.) I
guess the service name also wasn't added because it'd make some lines
really long, and because the journal can be queried for it anyway (-o
verbose, etc).
--
Mantas Mikulėnas
___
systemd-de
;
> And some discussion on libreoffice pages seems to be indicating that
> 'systemd --user' isn't supported any more.
Specifically, running `systemd --user` directly is not supported
anymore. The user mode still works, but only for one "user" instance
per UID
itself (pid 1).
> My guess was that the name of this program would be listed *in* the
> *.mount file, but that does not appear to be so.
That would not make any sense: if the program wasn't running yet, how
could it possibly start itself in
If not backslash-escaped, it splits the rule in two.
---
rules/80-net-setup-link.rules | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/rules/80-net-setup-link.rules b/rules/80-net-setup-link.rules
index 27c43b9..4207694 100644
--- a/rules/80-net-setup-link.rules
+++ b/rules/8
as soon as the
variable goes out of scope.
systemd uses this liberally, and has convenience macros like
_cleanup_close_ to automatically close fd's when returning from a
function, so they don't actually leak when declared like that.
The message you linked to actually describes exactl
:
https://bitbucket.org/bcsd/uselessd (or slashdot, phoronix, etc.)
>> Debian Bug report logs - #746715
>> the foreseeable outcome of the TC vote on init systems
>> https://bugs.debian.org/bug=746715
>
> "this package no longer exists" ?
https://bugs.debian.o
gt;
> Regards,
>
> T G-R
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
g. the
init) should work the same.
`ip netns` only shows "persistent" namespaces which were given a name
using the same tool. Containers generally don't bother with that.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@l
S/CIFS shares on boot) – unless I missed something,
`rpc.gssd` still only looks for FILE:/tmp/krb5cc_$UID and
DIR:/run/user/$UID/krb5cc...
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop
does your .service have an [Install] section?
///
I suggest using `k5start` instead, as a regular `kinit` will just
obtain a ticket but won't do anything when it expires in a few hours.
[Unit]
After=network.target
[Service]
Type=forking
ExecStart=/usr/bin/k5start -k FILE:/tmp/krb5cc_host -L -b -K 30 -f
/etc/krb5.keytab -u host/asmtp.gjn.prv
Restart=on-failure
[Install]
WantedBy=multi-user.target
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Oct 6, 2014 12:54 AM, "Aleksei Besogonov"
wrote:
>
> On 05 Oct 2014, at 11:02, Andrei Borzenkov wrote:
> > В Fri, 3 Oct 2014 22:55:13 -0700
> > Aleksei Besogonov пишет:
> >
> >> With all the recent noise about systemd abusing its position with the
way it takes over logging I’ve been thinking
Even though the 'emergency' and 'single' aliases come from sysvinit, the
lack of 'rescue' is still quite confusing (caught me by surprise for the
9th time yet) and inconsistent with `systemctl rescue` as well.
---
src/core/main.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/core/main.c
d work.
>
Hmm, isn't this basically the same as adding identical [Install] Alias=
entries, and using `systemctl enable -f` to manage them?
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
nsole-setup [1], but only if the
system locale is a UTF-8 one [2].
[1]:
http://cgit.freedesktop.org/systemd/systemd/tree/src/vconsole/vconsole-setup.c?h=a158dbf156ac#n70
[2]:
http://cgit.freedesktop.org/systemd/systemd/tree/src/shared/util.c?h=a158dbf1
ile, I get an error.
Recent systemd versions allow this if an ExecStop= is specified instead.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
es much easier to review.
I'm sure the patches are applied using `git am`, so that should work fine.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
irst, followed by $EDITOR...
(But in practice nobody sets them to different values anyway, since no
programs aside from mailx care about the distinction. So it's fine
either way, and just ignoring $VISUAL would be just as good.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fri, Oct 17, 2014 at 3:11 PM, Lennart Poettering
wrote:
> On Fri, 17.10.14 14:29, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
>> > Technically proficient people will set $EDITOR or $VISUAL
>> > anyway. Non-technical people won't. Non-technical people are likel
rn until
>> > the job of user@.service is done. `systemd --user` notifies READY=1
>> > only after "default.target" is ready.
> Hm, this seems a bit excessive, because default.target can take
> a while. basic.target would seem more natural.
Same -- I never noticed this since I have linger enabled, but I would
be a bit worried about the login blocking until /all/ of my services
have started... Which makes socket activation not very useful.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
opposed to changing this to basic.target. The
> important thing I guess is that after login all services are
> connectable, hence socket.target and busnames.target should have been
> reached at least, which basic.target delivers as much as
> default.target does...
Personal user services (dro
ve
> > session (since it is not launche from my active session) so it gets
denied
> > by policykit.
>
> policykit really should get fixed there. it shouldn't try to do access
> control for individual sessions but for users on specific
> sessions.
Wasn't this already fixed in polkit.git recently?
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Oct 23, 2014 5:48 PM, "Lennart Poettering"
wrote:
>
> On Thu, 23.10.14 16:06, Damien Robert (damien.olivier.rob...@gmail.com)
wrote:
>
> > >From Lennart Poettering, Thu 23 Oct 2014 at 14:01:22 (+0200) :
> > > Oh indeed, there is not sysinit.target. It sounded so wron in a user
> > > context...
mp; exports variables, then just `exec`'s the actual
daemon.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
curs when $LANG is being set in the
wrong place (e.g. ~/.bashrc), so the shell has it but the terminal
emulator doesn't. You can verify this by checking
"/proc//environ".
* Various layers like tmux or screen can also have the same problem as
X11 terminals above ($LANG
Usually there are a few delay inhibitors all the time (NetworkManager,
Telepathy, etc.), but I'm only interested in the block ones.
---
src/login/inhibit.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/src/login/inhibit.c b/src/login/inhibit.c
index d5ea1d9..122c69d 10
mand to "scan each user". To start multiple
units at once, make the target want all of them individually:
mailserver.target.wants/fetchmail@user1.service, and so on.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Wed, Nov 12, 2014 at 7:13 PM, Lutz Vieweg wrote:
> On 11/11/2014 08:35 PM, Mantas Mikulėnas wrote:
>
>> Anyway, there is no command to "scan each user". To start multiple
>> units at once, make the target want all of them individually:
>> mailserver.target.
;
> > ...but it would be nice if the behavior matched xinetd.
>
> You can do it in shell by parsing instance name embedded
> in /proc/self/cgroup
>
I'm not sure whether the instance names are something that should be relied
on?
(Not to mention that it'll probably take t
uching the service again.
What are the actual problems caused by this? (I'm guessing something might
rely on `hostnamed` watching /proc/sys/kernel/hostname, or things like
that?)
Maybe the services could have Subscribe() methods to cause them to stick
around...
--
Mantas Mikulėnas
__
ator, another by gpt-generator), systemd tries to swapon it
twice, resulting in "swapon failed: Device or resource busy".
This was broken first when systemd-gpt-generator appeared, then systemd was
taught to recognize duplicates, but now it seems to be broken again. (I
*think* it broke aroun
ctly.
>
You sure about that? /sys/class/rfkill/%i should work fine...
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Fa0/7)
>
> Would it be possible to implement this in networkd?
>
lldpd has the same feature... In fact, I'm curious what advantages will
networkd's implementation have over the existing lldpd and ladvd?
--
Mantas Mikulėnas
___
sy
On Mon, Nov 24, 2014 at 2:59 AM, Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> On Thu, Nov 20, 2014 at 09:13:02AM +0200, Mantas Mikulėnas wrote:
> > ~ If there are two .swap units for the same partition (one made by
> > fstab-generator, another by gpt-generat
On Mon, Nov 24, 2014 at 5:57 PM, Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> And what does 'udevadm info /dev/sda7' and 'systemctl show dev-sda7.swap'
> and
> the same for dev-disk-by\x2dpartlabel-swap.swap?
>
Attached both.
--
Mantas Miku
all "sd_notify"
> to send "READY=1"? I can't find the related code in system. Or the program
> itself?
>
Yes, it has to be added to your program. That's the whole point of
Type=notify, after all – systemd can't know when your progra
rt, and do its thing in ExecStop. So it'd be started after
everything else, do nothing, and be stopped before everything else.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
x.)
It's possible to emulate "import-environment" using:
xargs -d '\0' systemctl --user set-environment < /proc/self/environ
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Following commit 59580681f5f.
---
man/systemd.network.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/systemd.network.xml b/man/systemd.network.xml
index 11b4370..1edaa0b 100644
--- a/man/systemd.network.xml
+++ b/man/systemd.network.xml
@@ -429,7 +429,7 @@
;.disabled" as suffix is the easiest option,
> but maybe somebody has better ideas?
How about ignoring the file if .masked exists? touch/rm is a bit
easier than renaming.
Was thinking earlier about suggesting that for generators (which can't
really be renamed).
--
Mantas Mikulėnas
>
rescue.target pulls in sysinit.target (mounts, swaps, udev, sysctl...),
while emergency.target starts a sulogin shell and nothing more. See the
graph in bootup(7).
The sysv "single-user mode" maps directly to rescue.target.
--
Mantas Mikulėnas
___
iod of time,
> such as 3 restarts in 10 minutes, etc.
>
Sure, see StartLimit{Interval,Burst,Action}= in systemd.service(5).
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Thu, Nov 20, 2014 at 9:13 AM, Mantas Mikulėnas wrote:
> ~ I'm also getting this on every reload:
>
> systemd[1]: [/usr/lib/systemd/system/systemd-journald.service:24] Failed
> to parse capability in bounding set, ignoring: CAP_AUDIT_READ
>
> I suppose I can ignore
s this a bug or does
`systemctl status` simply show a different parameter now?
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
s
launchd.)
A.socket:
> [Unit]
> DescriptionA socket
> [Socket]
> ListenStream=/path
> SocketMode=0600
> Service=A.service
>
This "Service=" setting is redundant.
B.service:
> [Unit]
> Description=B, a tool talking to A
> Requires=A.service
>
Instea
Otherwise this actually remains in the generated unit in /usr/lib.
If you want to keep it commented out, a m4-compatible way would be:
m4_ifdef(`HAVE_SMACK',
dnl Capabilities=cap_mac_admin=i
dnl SecureBits=keep-caps
)
---
units/u...@.service.m4.in | 4
1 file changed, 4 dele
ordinates in curlies on general principle.
>
> For the sake of brevity our CODING_STYLE docs suggest to leave out
> unnecessary curly braces. Single-line code blocks should not be
> enclosed in them, this is not PHP after all...
>
There's no difference between C and PHP in th
ny tiling WM, they all have ways to autostart
programs. Most of them support the XDG Autostart
<http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html>
specification. Put this in ~/.config/autostart/synapse.desktop:
[Desktop Entry]
Type=Application
Name=Synapse
Exec=/usr/bin/synapse
Since the manpage already talks about shell-compatibility, it should be
more accurate about what needs to be escaped and how.
---
man/os-release.xml | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/man/os-release.xml b/man/os-release.xml
index b298304..b4cbe
almost always
in the root partition, isn't it?
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
rvices. In the future, the entire session might
be started through `systemd --user`.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
udev_device_get_parent() may return NULL when the device doesn't have a
parent, as is the case with (for example) /sys/devices/virtual/drm/ttm.
Also, log an actual error message instead of "-12 displays connected".
---
src/login/logind-action.c | 4 +++-
src/login/logind-core.c | 2 +-
2 files
---
src/nspawn/nspawn.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/nspawn/nspawn.c b/src/nspawn/nspawn.c
index cd31bd4..489dbde 100644
--- a/src/nspawn/nspawn.c
+++ b/src/nspawn/nspawn.c
@@ -2264,8 +2264,8 @@ static int spawn_getent(const char *database, const char
f you ran `make install`, however, it would chown /var/log/journal to
0:0 until the next time systemd-tmpfiles ran.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
;s
private socket or to enable the "user bus" somehow and connect to that. The
option expects a single user bus (which is still a future thing), instead
of the current per-session bus that it's currently trying to find your
systemd --user instance on...)
[1] http://www.freedesktop.org/wiki
On Mar 18, 2014 8:19 PM, "Lennart Poettering"
wrote:
> …
> Well, the ELF interpretor stuff means noexec is pretty much entirely
> useless.
If by this you mean running '/lib/ld-linux.so.2' directly, that does not
work with noexec anymore, due to the aforementioned mmap restriction AFAIK:
"/mnt/te
t; There is a typo: should be ExecStop and not Execstop
This seems like a distribution specific unit; systemd itself certainly does
not ship any .service that would use /sbin/ip.
(In v211 there is systemd-networkd and earlier versions just didn't hav
case – 'su'
probably should not create a new login session, it should remain in the
previous one. On the other hand, there were a few threads about just how
much 'su' and 'sudo' are meant to change...It also depends on whether
su/sudo are invoked *from* within an existing session (they should always
be).
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
CM0` to see the subsystem and the ENV{} variables
that you can match against, and let the rule check also attrs of _parent_
devices using ATTRS{} instead of ATTR{} (if these matches are necessary in
the end; I think env matches will be simpler).
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
ccess is
removed, since logind has no way of knowing that vt7 is being used by your
processes.
You have already found the correct way to fix this – start X on the
*same*vt that you logged in (e.g. `startx -- vt2` or `startx --
vt$XDG_VTNR`).
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
option for that.
(As a workaround, if you require X11 on vt7, you can start
getty@tty7.service, and startx there.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
---
src/login/logind-dbus.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/login/logind-dbus.c b/src/login/logind-dbus.c
index 0af6714..0e58955 100644
--- a/src/login/logind-dbus.c
+++ b/src/login/logind-dbus.c
@@ -1922,6 +1922,10 @@ const sd_bus_vtable manager_vtable[] = {
S
On 2014-04-20 21:45, Matthew Monaco wrote:
> And of course, the third option would be to submit a patch. The src/cryptsetup
> stuff is pretty straightforward.
Wasn't one submitted just a month ago?
--
Mantas Mikulėnas
___
systemd-devel m
it takes to lookup and output the data)
strace shows that it isn't looking up any data; it's actually waiting
for inotify events for the --follow mode. Seems odd.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@list
t version that Arch has – only shows the
first address to this day.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
With proprietary graphics drivers, there won't be any 'drm' devices in
sysfs, so logind will never suspend the system upon closing the lid,
even if only one (internal) display is connected. This has been reported
by multiple users so far.
IMHO, it's better to suspend the system in this case for sa
With proprietary graphics drivers, there won't be any 'drm' devices in
sysfs, so logind will never suspend the system upon closing the lid,
even if only one (internal) display is connected. This has been reported
by multiple users so far.
IMHO, it's better to suspend the system in this case for sa
901 - 1000 of 1190 matches
Mail list logo
