, isn't it?
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
. In the future, the entire session might
be started through `systemd --user`.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
---
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
`, however, it would chown /var/log/journal to
0:0 until the next time systemd-tmpfiles ran.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
), 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/Software/systemd/dbus/
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel
On Mar 18, 2014 8:19 PM, Lennart Poettering lenn...@poettering.net
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
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 have
any network configuration.)
--
Mantas Mikulėnas graw...@gmail.com
an existing session (they should always
be).
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
are necessary in
the end; I think env matches will be simpler).
--
Mantas Mikulėnas graw...@gmail.com
___
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[] = {
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 graw...@gmail.com
___
systemd-devel
overhead 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 graw...@gmail.com
___
systemd-devel mailing list
systemd-devel
has – only shows the
first address to this day.
--
Mantas Mikulėnas graw...@gmail.com
___
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
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
systemd-timer is triggered.
Doesn't the kernel already do the same via CONFIG_RTC_HCTOSYS_DEVICE?
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd
On Mon, Apr 28, 2014 at 6:10 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 28.04.14 00:44, Mantas Mikulėnas (graw...@gmail.com) wrote:
With proprietary graphics drivers, there won't be any 'drm' devices in
sysfs, so logind will never suspend the system upon closing the lid
---
man/journald.conf.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 239a2ec..5cd09a2 100644
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -190,8 +190,8 @@
limiting is
services.
[1] It's possible to use user@.service in some older systemd versions
as well, but it's not auto-started until v205, and there are other
small differences.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel
'(permitted) = (P(inheritable) F(inheritable)) | (F(permitted) cap_bset)
...and as effective on the file, otherwise the new process has to
manually 'enable' them:
P'(effective) = F(effective) ? P'(permitted) : 0
...or at least that seems to be how it works. Damn thing is confusing.
--
Mantas
. The systemd-rfkill@ units are invoked by udev rules
with the exact name from kernel, so a rfkill1 must have been there at some
point, and disappeared very quickly afterwards? (There wouldn't be a hole
in the numbering otherwise, too.)
--
Mantas Mikulėnas graw...@gmail.com
On Wed, May 28, 2014 at 1:37 PM, Michal Witanowski
m.witanow...@samsung.com wrote:
On 05/28/2014 12:07 AM, Serge Hallyn wrote:
Quoting Mantas Mikulėnas (graw...@gmail.com):
On Tue, May 27, 2014 at 4:31 PM, Michal Witanowski
m.witanow...@samsung.com wrote:
Hi,
first of all I'd like
seats?
I think the difference is that with `jstest`, the device doesn't
interact with your seat, but *you* are interacting directly with its
device node, so the only thing that's checked is devnode
permissions...
--
Mantas Mikulėnas graw...@gmail.com
So the seat assignment works fine – gdm is added to the ACL.
The problem is that the devnode is *world-readable*.
--
Mantas Mikulėnas graw...@gmail.com
On May 28, 2014 8:57 PM, Floris jkflo...@dds.nl wrote:
Op Wed, 28 May 2014 19:06:22 +0200 schreef Zbigniew Jędrzejewski-Szmek
zbys
find a WiFi
AP before an IP address can be assigned at all.
Instead of configuring these parts manually, I suggest trying out
NetworkManager, connman, wicd, or Arch's netctl – all of which can connect
to a wired/wireless network and set up everything at once.
--
Mantas Mikulėnas graw...@gmail.com
I would suggest people who need a syslogd to use syslogd. Specifically,
rsyslog, which can also output to the journal using the 'omjournal' module,
(besides the aforementioned normalization features).
--
Mantas Mikulėnas graw...@gmail.com
On Jun 1, 2014 8:26 AM, Lennart Poettering lenn
(i.e. a
byte-array of the 16 raw uuid bytes instead of an ascii-formatted
string). This is how we encoded UUIDs so far as bus properties, see
machined's machine uuid property (src/machine/machine-dbus.c) for example.
Thanks!
Lennart
--
Mantas Mikulėnas graw...@gmail.com
---
man/sd-journal.xml | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/man/sd-journal.xml b/man/sd-journal.xml
index 7a05aee..d3dc57f 100644
--- a/man/sd-journal.xml
+++ b/man/sd-journal.xml
@@ -79,7 +79,8 @@
all the other link types that Linux supports though.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
/systemd/journal-files/:
Clients intending to show a live view of the journal should use inotify() for
this to watch for files changes.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
There are. You have socket-activated services, and you have services that
bind to 0.0.0.0 or ::, and you have services that make use of IP_FREEBIND
to avoid having to wait for addresses to be assigned...
--
Mantas Mikulėnas graw...@gmail.com
On Jun 8, 2014 2:27 AM, Leonid Isaev lis
disabled IPv6 intentionally in my customized kernel
For the record, what good reason is there for doing that?
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman
I think there's also another problem – logind starts the user manager
instance for cronjobs while it shouldn't do so for batch stuff. Probably a
PAM configuration issue.
--
Mantas Mikulėnas graw...@gmail.com
On Jun 9, 2014 9:34 AM, Leho Kraav l...@kraav.com wrote:
After upgrading systemd 208
---
units/user/systemd-bus-pro...@.service.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/units/user/systemd-bus-pro...@.service.in
b/units/user/systemd-bus-pro...@.service.in
index 68f59f5..2f4df7c 100644
--- a/units/user/systemd-bus-pro...@.service.in
+++
of unit
dependencies.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hmm, didn't this get fixed in recent versions? I seem to remember that
after the sd-bus port systemd started sending changed_properties with
values, not just invalidated_properties...
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
On Jun 11, 2014 12:59 PM, david.ya...@continental
, though most distros have
it as just a shell script.)
Try the boot options loglevel=6, systemd.log_level=debug, or init=/bin/sh.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
---
NEWS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index 54d9e9e..1effaf5 100644
--- a/NEWS
+++ b/NEWS
@@ -52,7 +52,7 @@ CHANGES WITH 214:
transports. Instead it is assumed the kernel loads them
automatically when required. This only
not
be able to find inittab and gets lost or something.
No; systemd does not use that file. It is configuration for SysV init only.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
. In your log, it doesn't even attempt to boot because
of different PID, so the log isn't particularly useful.)
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman
(/sys/fs/smackfs/load2, O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC,
0666) = -1 ENOENT (No such file or directory)
systemd is checking if it should load SMACK or IMA policy; this can be
safely ignored if you don't use these security modules.
--
Mantas Mikulėnas graw...@gmail.com
to systemd.
- When it hangs, reboot again with init=/bin/sh,
- and use `journalctl --boot -1` to get the previous boot's log.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org
or
emergency mode (single or emergency as kernel parameters) and try
starting multi-user.target manually...
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
On Jun 13, 2014 12:19 PM, Jay D Bhatt jay.bh...@igate.com wrote:
Sorry, Forgot to send log.
I got the previous log by command use
it would be useful to send a patch for
including it along with systemd's default rules...
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman
installation, and
stored in /etc/machine-id. It only changes on diskless systems or if
/etc is unwritable for some other reason. (systemd can get the machine
ID from /sys/class/dmi/id/product_uuid, but only does so on qemu-kvm
VMs.)
--
Mantas Mikulėnas graw...@gmail.com
(whether static or not)? Having them static won't make any difference.
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
On Jun 17, 2014 2:14 PM, Runiq ru...@archlinux.us wrote:
Hello all,
I'm using systemd 213 on Arch Linux, and systemd-networkd/resolved with
DHCP to connect
to look in /run/systemd/resolv.conf for the upstream
servers' addresses. I'm sure at least dnsmasq has that ability.
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
On Jun 17, 2014 2:14 PM, Runiq ru...@archlinux.us wrote:
Hello all,
I'm using systemd 213 on Arch Linux, and systemd
of some user activity?
I think this is usually done by comparing if the clock after wakeup ==
(clock before wakeup + hibernation delay + ...maybe clock drift?).
[In other words, ugly hack from before s2both days.]
--
Mantas Mikulėnas graw...@gmail.com
learns keyctl_ssh_{rsa,ecdsa,ed25519}_sign()
or another similar interface that will always take 2-3 years to catch up
every time the user space learns a new cipher or protocol...
(I am reminded of plan9's Factotum, which was kind of like ssh-agent but
part of the OS...)
--
Mantas Mikulėnas graw
A session manager is *not necessary* for this; the screensaver or
screenlocker itself could easily listen to the relevant DBus signals (e.g.
cinnamon-screensaver does this). See also: xss-lock, systemd-lock-handler.
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
On Jun 29, 2014 1:02 PM
for the long run).
User services work quite well for such things already, only the X11
and DBus session-bus access is still problematic. Should be fine for
Unison.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel
about IP address rewriting or masquerading,
*not* lifetimes/expiry? Confused.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
is part of sd-bus nowadays, as far as I know, and it
still seems to be there on my yesterday's Git build.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo
to serialize startup.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Afaik, XDG defines $XDG_DATA_HOME or ~/.local/share to be the location for
such data, and various other chat clients use it for logs (it doesn't
exactly match /usr/share because XDG doesn't care for the rest of ~/.local).
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
On Jul 4, 2014 12
' in the kernel command line?
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
fsck even work if /dev/root is NFS?)
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
NotifyAccess=all
FailureAction==reboot-force
[Install]
WantedBy=multi-user.target
(Also, please do not use `pkill` in ExecStop; it's not just unnecessary, it
even makes the stop process *less* reliable. systemd already knows which
PID it has to kill.)
--
Mantas Mikulėnas graw...@gmail.com
Sounds like a better fit for /etc/machine-info, as it's really not a distro
thing.
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
On Jul 7, 2014 10:41 PM, Jóhann B. Guðmundsson johan...@gmail.com wrote:
Hi
I've noticed repeated problem through history where administrators seem
shutdown – your service will be stopped *after* all sessions are removed.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Turns out, making strings shell-proof is harder than expected:
# machinectl set-hostname foo|poweroff . /etc/machine-info
(This could be simplified by quoting *and* escaping all characters,
which is harmless in shell but unnecessary.)
---
src/shared/fileio.c | 4 ++--
src/shared/util.h |
'tmpfs'es.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
For testing, if the nss module is installed but not configured,
`getent --service=resolve ahosts google.com` might work...
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
@*.service units as base for your
custom ones. (The administrator overrides in /etc always take priority
over generated and package-distributed units in /run and /lib.)
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel
, in which case the
existing ListenSequentialPacket would work?
Maybe there should be some syntax for specifying the protocol in
ListenStream/ListenDatagram, to allow for various odd things like
stream/SCTP and dgram/UDPLITE etc.
--
Mantas Mikulėnas graw...@gmail.com
if the configuration is fine in the beginning, but another admin
breaks it while your rsync is running?
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman
resolving
google.com.example.com. and only then google.com. unless I manually added
. at the top of the list...
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
* programs (journald, journalctl,
netcat) that only do a halfassed job compared to rsyslog *isn't* a problem
anymore...
--
Mantas Mikulėnas graw...@gmail.com
// sent from phone
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
; 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 graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo
://thread.gmane.org/gmane.comp.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 graw...@gmail.com
, 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.) If
not, one should be easy to write, and it'll protect *all* login
methods.
--
Mantas Mikulėnas graw
at the same time.
As for the terms... it seems that the general stages are inactive,
activating (in the startup process), active (has finished
startup), and deactivating. I'm not entirely sure what stages apply
to .service units.
--
Mantas Mikulėnas graw...@gmail.com
– they're only a way to represent device status in
the format of systemd units. In other words, they do not cause the
problems you're having; they only make the problems visible in your
bootchart.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel
-gmac/net/eth0
/sys/devices/platform/tcc-uart.0/tty/ttyTCC0
/sys/devices/platform/dwc_otg.0/gadget/tty/ttyGS0
...what kind of a device is it, anyway? A raspberryπ?
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel
.)
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
this is hardware-dependent... In my case, it looks like the
opposite – the firmware /does/ remember brightness for me, but during
boot something resets it to maximum.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel
, `systemctl start user@1000.service` does not work)
It /should/ work, because that's exactly how logind starts it.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman
everyone that they're using a multi-user OS.
Then there are minor things like $DBUS_SESSION_BUS_ADDRESS,
$SSH_AUTH_SOCK, $SESSION_MANAGER, $GPG_AGENT_INFO...
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel
.
Normally, you also need to set XAUTHORITY= to the right path --
since you do not want just anybody to be able to connect to your :0.
Xorg also allows giving access by UID, using `xhost
SI:localuser:$UID`, which removes the requirement to have access to
Xauthority data.
--
Mantas Mikulėnas graw
pam_deny.so
account include system-login
session include system-login
password required pam_deny.so
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman
systemd-sysctl gives priority to the latest occurence as of commit
04bf3c1a60d82791e0320381e9268f727708f776, but the manpage hasn't been
updated for that.
---
man/sysctl.d.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/sysctl.d.xml b/man/sysctl.d.xml
index
Sync with user_bus_path() in logind-user-dbus.c
---
src/login/logind-dbus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/login/logind-dbus.c b/src/login/logind-dbus.c
index ec590c0..e76381b 100644
--- a/src/login/logind-dbus.c
+++ b/src/login/logind-dbus.c
@@ -2256,7
, I propose this simple change to
make user sessions a little bit nicer out of the box.
Right; this is exactly the kind of thing that would be fixed by having
logind run the PAM stack and pass the environment/state to systemd-user.
SHELL is set by /sbin/login, not by PAM.
--
Mantas Mikulėnas
.
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
/linux || {
+cp $KERNEL_IMAGE $BOOT_DIR_ABS/linux
+ chown root:root $BOOT_DIR_ABS/linux
+ chmod 0600 $BOOT_DIR_ABS/linux || {
How about `install -m 0600 -o root -g root`?
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
org.freedesktop.DBus.Properties interface. (Although systemd
only sends invalidated_properties and the new values have to be
retrieved manually, so that's not really perfect yet.)
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
On Thu, Oct 3, 2013 at 3:06 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Thu, 03.10.13 06:05, Mantas Mikulėnas (graw...@gmail.com) wrote:
This is already handled by the PropertiesChanged signal in the
standard org.freedesktop.DBus.Properties interface. (Although systemd
only sends
/bin/autologin
PAMName=login
Name=daniel
There is no such directive as Service.Name -- if you want to specify
the username, you need Service.User instead:
[Service]
User=daniel
Group=users
See the systemd.exec and systemd.directives manual pages.
--
Mantas Mikulėnas graw
Because that's exactly the kind of situation where the private bus is
necessary.
---
src/core/manager.c | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/src/core/manager.c b/src/core/manager.c
index 58dacdc..e183325 100644
--- a/src/core/manager.c
+++
It seems that some places use /run otherwise, which isn't going to work.
---
src/core/main.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/src/core/main.c b/src/core/main.c
index fe291f8..36543c6 100644
--- a/src/core/main.c
+++ b/src/core/main.c
@@ -1404,6 +1404,12 @@ int main(int
to bus_init_private() a little
higher.)
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
. RuntimeMaxFileSize=1M,
RuntimeMaxUse=16M).
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
is created at all... or in other words,
why systemd looks in /usr/share and ~/.local/share for user units in
the first place? It is neither documented in systemd.unit(5), nor
consistent with the system unit paths, nor makes much sense since
AFAIK the units are configuration, not data?
--
Mantas
Otherwise 'not-found' overflows into the ACTIVE column.
---
src/systemctl/systemctl.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index 9f5e273..04699be 100644
--- a/src/systemctl/systemctl.c
+++
, and in other cases with a broadcast address. We should at
least try to normalize this into different sections, no?
Hmm, when is explicitly setting the broadcast address ever necessary?
--
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing
. GNOME dconf
uses [foo/bar/baz] when exporting hierarchical configuration; sssd's
configuration is simpler, but it still has [foo/bar] in some places.
Similarly, Windows .reg files – exported Registry branches – use
[foo\bar\baz].
--
Mantas Mikulėnas graw...@gmail.com
---
src/systemctl/systemctl.c | 19 +++
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index 8b6dae2..737cd67 100644
--- a/src/systemctl/systemctl.c
+++ b/src/systemctl/systemctl.c
@@ -1445,11 +1445,12 @@ static
---
src/activate/activate.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/activate/activate.c b/src/activate/activate.c
index dffc6e2..2639d1c 100644
--- a/src/activate/activate.c
+++ b/src/activate/activate.c
@@ -289,6 +289,8 @@ static int help(void) {
-l
getopt_long() was told to accept -s which was never implemented.
---
src/activate/activate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/activate/activate.c b/src/activate/activate.c
index 07e46b9..dffc6e2 100644
--- a/src/activate/activate.c
+++
is a bit annoying.
Is this by design or a simple left-over?
If *everything* moved to /usr/bin, then /bin itself has to be a
symlink anyway (as many tools expect and some standards require
specific commands to be in /bin).
--
Mantas Mikulėnas graw...@gmail.com
1 - 100 of 1110 matches
Mail list logo
