> where squid (for example) is the daemon itself; but nsenter allows me
> to run it in that namespace?
>
> Just confused about whether that's technically one command or not...
>
It is.
> can I still use Type=Simple?
Usually `nsenter` directly
r all rules have been processed.
Or in other words, anything you do via udev rules happens *before* all
other daemons consider the device "ready". (After all, udev rules are often
what *make* the device ready for use.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
h of them manually , they are working as expected.
>
> If I start as system service, it is taking around 2 minutes for data to
> reach from app1 to app2.
>
> What can be the possible reasons?
>
How did you measure this? Can you provide a
.
>
Unless you start them in a specific manner that places them inside the
session. (If I remember earlier threads correctly, and I'm assuming deepan
is still working on the same system as before, then this is some sort of an
embedded system where every
`grep mmcblk1 /proc/*/mountinfo` should do the job as well.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
`systemd-mount` tool if your version comes with it. That
will create a transient .mount unit in systemd via IPC, so it will be
unaffected by namespacing.
Otherwise, no need to bother with MountFlags=, just remove the existing
PrivateMounts=yes option which isolates udev to begin with.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
rd and it's always called "card0":
[Unit]
Requires=dev-dri-card0.device
After=dev-dri-card0.device
(Note: This also needs udev/rules.d/99-systemd.rules to be extended with an
apropriate TAG+="systemd".)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
;possessor" has full permissions, but the "uid/gid/other" have none.
(e.g. keyctl
setperm 0x3f00).
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
at's being called in ExecStart.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
doesn't
> support that operation" when I attempt a "ln -s".
>
Try adding the additional mount units to the base .mount's Wants= and
Before=.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedeskt
table would be nice (at least for
DBus-incapable shell scripts). You could then feed that to `jq`.
(I wonder if systemctl could use libsmartcols from util-linux...)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.or
These looked like a mass-replace gone slightly wrong – two statements
with no { }'s, and no error checking.
---
src/core/busname.c | 4 +++-
src/core/manager.c | 5 -
src/core/socket.c | 3 ++-
3 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/src/core/busname.c b/src/core/busnam
Following commits fe506d569d82467f3186 and 190700621f95160d364f.
---
src/libsystemd-terminal/grdev-drm.c | 9 +++--
src/libsystemd-terminal/idev-evdev.c| 3 +--
src/libsystemd-terminal/idev-keyboard.c | 8 +++-
src/libsystemd-terminal/idev.c | 6 ++
src/libsystemd-
h*. The
whole point of SIGABRT is that it kills the program immediately, when the
program calls abort() after detecting some serious inconsistency.
It is also not a bug that the kernel panics when init exits. Several things
depend on the existence of PID 1.
--
Mantas Mikulėnas
__
o systemd catches these signals but enters "crash mode"
immediately.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Mon, May 4, 2015 at 3:40 AM, Lennart Poettering
wrote:
> On Sun, 03.05.15 19:10, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
> > On Sun, May 3, 2015 at 6:54 PM, Víctor Fernández
> wrote:
> >
> > > Ok, Thanks for your reply.
> > >
> > > But, j
on's answer for a much better
solution (using udev ACLs).
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-d only with stop it could as
> well be a single option that works for both?
>
Would be less of a problem if subcommands could have their own options
separate from global ones...
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel
orate firewalls and embedded devices (i.e. home gateways) which choke
on EDNS, crash upon seeing DNSSEC, truncate all packets to 512 bytes
(manufactured in 2015!), and even outright lie – by making up their own
(incorrect) responses instead of forwarding the query. (If it's not
encrypted,
On May 16, 2015 11:18, "Per Bergqvist" wrote:
>
> Lennart,
>
> Thank you for all the comments.
>
> I have changed everything except the 'No space between function name and
opening “(“‘.
> Cannot find anything about that in CODING_STYLE or evidence in other
sources.
"Most every call in the entire
truncates
> DNS packets, then switch over to establish a TCP connection for DNS and
> start using that one. Meaning in case the result is too large to fit in
> over UDP, make the same request over TCP and deliver that result to the
> clients. At that point, you can also
---
Makefile.am | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile.am b/Makefile.am
index 4639b2f..0b5b488 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -3913,6 +3913,7 @@ dist_udevhwdb_DATA = \
hwdb/60-evdev.hwdb \
hwdb/60-keyboard.hwdb \
hwdb/70-mouse.hwdb \
+
---
*sigh* Tabs.
Makefile.am | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile.am b/Makefile.am
index 4639b2f..5bcbfff 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -3913,6 +3913,7 @@ dist_udevhwdb_DATA = \
hwdb/60-evdev.hwdb \
hwdb/60-keyboard.hwdb \
hwdb/70-mo
NetworkManager has
> configured the bridge and failing because it cannot bind to the bridge's
> IP address.
>
dnsmasq has the "bind-dynamic" option for such situations.
--
Mantas Mikulėnas
___
systemd-devel mailing list
s
child PID.
(I'm using Arch Linux with the traditional mkinitcpio-based initramfs,
which starts udev using "systemd-udevd --daemon --resolve-names=never".)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedes
systemd-udevd --daemon --resolve-names=never".)
>
> Thanks for the report. This should be fixed now in git, please let me
> know if that is not the case.
>
> Cheers,
>
> Tom
>
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
replace the session bus yet, but
you *will* be able to connect to it and reach systemd, at address
"kernel:path=/dev/kdbus/$UID-user/bus;unix:path=$XDG_RUNTIME_DIR/bus".
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Tue, May 26, 2015 at 10:32 PM, Chris Morgan wrote:
> On Tue, May 26, 2015 at 3:22 PM, Mantas Mikulėnas
> wrote:
> > On Tue, May 26, 2015 at 9:33 PM, Chris Morgan
> wrote:
> >>
> >> But I can't seem to figure out how to do the same for user u
Well, the systemd side is already there – if you have kdbus, it'll create a
user bus there, and if you have traditional dbus.service + dbus.socket,
systemd will also happily connect to that.
On Tue, May 26, 2015, 23:46 Chris Morgan wrote:
> On Tue, May 26, 2015 at 4:05 PM, Mantas M
vileged clients. Normally it's the duty of dbus-daemon to enforce
> more complex policy on dbus1 systems. If you take dbus-daemon out of
> the equation however, then this policy component will be missing, and
> hence systemd refuses to talk to any unprivileged clients.
>
Hmm, in a kdbu
s he can
> enable/disable PA as per need. How can I disable PA in such a scenario?
>
You could set "autospawn = no" in pulse-client.conf(5).
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
unted, then it's mounted.
> And systemd-remount-fs.service will remount the root again, thus apply
> options in fstab?
>
Yes, such as rw.
> BTW, where are the units generated by generators?
>
/run/systemd/generator*/
--
Mantas Mikulėnas
___
o tell you that
something could *break* it.
> 4. *DAEMON_OPTS = " "* ? Probably, the value of this "DAEMON_OPTS" need
> to write in file: /*etc/default/xl2tpd *? If is so, I don't know, what
> must to write. My provider also can't help me.
>
The variable just contains the options that will be passed to
/usr/sbin/xl2tpd, for example:
DAEMON_OPTS="-c /etc/xl2tpd/xl2tpd.conf"
But usually xl2tpd doesn't need any special options, I think.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
implemented.
> >>
> >> Jean-Christian
> >
> >
> > Face your broadband modem, live your dreams?
> >
> > Kay, when this would happen - Predictable Broadband Modem Interface
> Names?
> >
>
> Wouldn't it be nicer to have symlinks like in /dev/disk ?
> /dev/tty/by-path/
60-serial.rules:16:ENV{ID_PATH}=="?*", ENV{.ID_PORT}=="",
SYMLINK+="serial/by-path/$env{ID_PATH}"
60-serial.rules:17:ENV{ID_PATH}=="?*", ENV{.ID_PORT}=="?*",
SYMLINK+="serial/by-path/$env{ID_PATH}-port$env{.ID_PORT}"
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
ifferent rules, and it is
frankly confusing as duck. But they aren't "broken" nor "ignored", no.
--
Mantas Mikulėnas
On Jun 8, 2015 23:00, "Lennart Poettering" wrote:
> On Wed, 03.06.15 19:18, Sébastien Luttringer (se...@seblu.net) wrote:
>
> > H
ot read from it. Early during boot, the system has very little entropy
available from other sources, so it is common to save some random data from
last boot and provide it to the PRNG later.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel
q+F will run the OOM
killer in case of heavy swapping, Alt+SysRq+E/I will sigterm/sigkill all
programs (systemd will restart gettys afterwards), and Alt+SysRq+N will
renice high-priority processes. You need to enable this via sysctl.conf
though.
--
Mantas Mikulėnas
___
rom the journal.
The journal, however, also receives messages sent using the traditional
syslog API or written to the kernel log – in addition to its native
sd_journal_send(3)
<http://www.freedesktop.org/software/systemd/man/sd_journal_send.html> – so
that already cover
On Jun 29, 2015 16:58, "Lesley Kimmel" wrote:
>
> Jonathan;
>
> Thanks for the background and information. Since you clearly seem to have
a grasp of systemd please humour me with a few more questions (some of them
slightly ignorant):
>
> a) Why are PID bad?
> b) Why are lock files bad?
> c) If a/b
d2cfd1395a97fa or similar scripts.
Also note that the primary repository is at
https://github.com/systemd/systemd these days.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
First, are you actually switching your bus connection to monitor mode? In
kdbus (and probably even in future DBus) there is a distinct monitor mode
which must be enabled to capture other peers' bus traffic. Adding a match
is not enough for that.
Second, your approach won't work anyway. There *won'
Options:
- Configure it as part of ExecStart if possible.
- Configure it using a second .service unit (oneshot), and depend on that
one.
- Do something with udev to mark unconfigured devices with SYSTEMD_READY=0?
Not sure how. But if you can do this, it'll directly affect the "readiness"
of the
quot;shutdown initramfs" feature [1]
would help here.
[1]: http://www.freedesktop.org/wiki/Software/systemd/InitrdInterface/
[2]: http://www.freedesktop.org/wiki/Software/systemd/RootStorageDaemons/
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
python-systemd/releases ?
>
> Btw, does anyone know if those release tarballs are generated by
> github on the fly and might have different md5sums?
>
They should be identical regardless – git-archive tries to generate
reproducible archives (assuming same pa
*systemd-networkd-wait-online.service*, which your unit can depend on. Note
that by default it waits for *all* interfaces to be configured; if you only
need a specific one, you can create your own (instanced/templated) version
that would use "--interf
Note that devpts also supports multiple instances – the host /dev/pts is
not the same as the guest /dev/pts'en. So my guess is that your stdio is
attached to a pty from the *host*.
Not really sure how that breaks job control though.
Also, the fd symlinks are slightly magical; they can be followed
?
>
"Runtime" here means /run, as opposed to persistent in /var. They have
separately configurable limits, since /run is in RAM and /var is usually on
disk. (Though, I'm not entirely sure what purpose the runtime journal even
serves, when /var is available.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
systemd/user,
and that's it. It'll be available to all users.
If you want to forcefully enable the service for all users, then also
symlink it into /usr/lib/systemd/user/default.target.wants/, which is
almost exactly what `systemctl enable` does (except system-wide). That'll
make
gt; days. And you can leave off the Signed-off-by line, we don't use that in
> the systemd project.
>
Does including it hurt though?
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesk
more experiences
> around the fine-tuning of such settings and their reuse
> for the generation of symbolic links by udev rules?
>
...??
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
tes:
>
> N starting data transfer loop with FDs [5,5] and [1,1]
> N socket 2 (fd 1) is at EOF
> I close(5)
> N exiting with status 0
>
socat uses bidirectional streams by default, so if it says it hit EOF on
"STDOUT", maybe it's treating it as ali
guess security would be a problem (how to determine which users may
receive which events).
--
Mantas Mikulėnas
On Jul 28, 2015 18:46, "Stef Bon" wrote:
> Hi all,
>
> for some time I have been looking at the issue why fsnotify does not work
> with network filesystems a
On Thu, Jul 30, 2015 at 4:20 PM, Sakhi Hadebe wrote:
>
> Jul 30 15:13:30 monitor.sanren.ac.za nagios[32281]: ***> One or more
> problems was encountered while processing the config files...
>
That sounds like a nagios problem?
--
M
git.kernel.org/linus/c4e00daaa96d
https://git.kernel.org/linus/3b552b92817c
Rsyslog can import the structured data from /dev/kmsg:
http://www.rsyslog.com/doc/v8-stable/configuration/modules/imkmsg.html
--
Mantas Mikulėnas
___
systemd-devel mailin
eating the new
instance directly. (Make a template foo@.service unit for the WLMS
instances.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
t doesn't care about the names), it
will just create a new one, and you'll have to re-do the above.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
l~, just in case.
> What is the correct procedure to remove them?
>
`rm`, or let journald's built-in log rotation take care of them.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
is no need for a signal – inotify can inform you about renames as
well.
But, you shouldn't reimplement the entire logic yourself. (There's more to
it, like separate systemd or user journals) *Instead, call
sd_journal_get_fd(3) and let libsystemd do the monitoring.*
--
Mantas Mikulėn
econd try, the kernel panics). I haven't gotten around to reporting it yet.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
full tmpfiles.d config, and tell the service to use
"/run/myservice/myservice.pid". It might be simpler than touch+chown, and a
bit cleaner.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
tworkManager could add rules for source-based
routing by default – it would make some configurations (like two default
routes) much easier to use...
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.fre
ot;, TAG+="uaccess"
>
> in usb-storage.rules ?
>
> You might wanna rename the rule to something like 90-usb-storage.rules,
> but thats besides the point.
Hmm, in fact, the "uaccess" tag is consumed by:
73-seat-late.rules:15:TAG=="uaccess", E
--user units
dbus.socket and dbus.service necessary for this. The user bus address is
"kernel:path=/dev/kdbus/$UID-user/bus;unix:runtime=yes" (if I got the
syntax right?), or
"kernel:path=/dev/kdbus/$UID-user/bus;unix:path=/run/user/$UID/bus".
(Technically the same can b
> *[igeiser] *Is this the method various “user units” howtos add a
> dbus.socket and dbus.service into the user directory? I will research the
> dbus repo for their details. This is happy lab fun time so I am play with
> hacks if they don’t lead me away from the official solution.
&g
x27;t know how at-spi works in general. But AFAIK it launches its own
separate bus anyway (I see dbus-daemon
--config-file=/etc/at-spi2/accessibility.conf), so it could continue doing
that.
--
Mantas Mikulėnas
___
systemd-devel mailing l
On Wed, Aug 19, 2015 at 7:13 PM, Simon McVittie <
simon.mcvit...@collabora.co.uk> wrote:
> On 19/08/15 14:12, Mantas Mikulėnas wrote:
>
> > The user bus address is
>
> ... tried by default in libdbus 1.9, GLib 2.45, and sd-bus; so you don't
> need to set DBUS_SE
CLs independently of
udev rules, but it only does so when switching sessions; it doesn't do
anything when a new device is connected.)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedes
ed in.
>
Hmm, and `findmnt` doesn't?
`systemd --user` runs with the same privileges as the user, anyway. So if
your SELinux policy is more permissive to systemd than regular programs,
it's a bit weird, not to mention possibly insecure.
--
Mantas Mikulėnas
_
On Fri, Aug 21, 2015 at 1:29 PM, Dominick Grift
wrote:
> On Fri, Aug 21, 2015 at 01:10:51PM +0300, Mantas Mikulėnas wrote:
>
>
> > >
> > > i think it kind of sucks that systemctl --user list-units can be used
> to
> > > determine who is currently logge
On Fri, Aug 21, 2015 at 1:43 PM, Dominick Grift
wrote:
> On Fri, Aug 21, 2015 at 01:38:28PM +0300, Mantas Mikulėnas wrote:
>
> >
> > Do they have access to `cat /proc/self/mounts`?
>
> Ouch yes... ok that is a dead end i suppose
Right. That was my point. Restricting
ugh it's actually a pitty. I believe it could be
> useful in some cases notably remote login, not quite sure though.
>
>
> W dniu 22.08.2015 o 16:58, Mantas Mikulėnas pisze:
>
> Well, you just wouldn't have more than one graphical session. That's part
> of the gener
t;" type errors.
>
> I assume it's because Xorg can't network to my local host's Xorg server.
> Any tips how to manage this mapping?
>
> I need network isolation going for accurate measurements from $(grep
> firefox /proc/net/dev), with hopef
red
attributes into ENV.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
kes it a bit easier to have the ESP remain
> unmounted or read-only when not in active use, which is good for its own
> robustness; a system crash corrupting an unmounted partition is less
> likely than corrupting a mounted filesystem.
>
Though, why would a partition get corrupted, if i
;" for integers larger than
0x7fff. (Possibly also explicitly pass the value as a dbus_int64()...)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
this:
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/xserverrc?h=packages/xorg-xinit&id=37b4597466e99667ba6035854b3386a2ee83e563
(note this is no longer present in Arch's xinit as it has been moved to
startx itself)
I don't know how startxfce4 launche
> I don't think there's any way to have
something auto-unmount
There certainly is – udev has been unmounting unplugged drives for many
years. It's done by default.
On Mon, Sep 21, 2015, 23:10 Paul D. DeRocco wrote:
> > From: Umut Tezduyar Lindskog [mailto:u...@tezduyar.com]
> >
> > I am not sur
ou asking the OS to be prescient?
> to avoid data loss. The only alternative is to disable write buffering,
> which makes things slow, and stresses the drive.
>
No, that's not the only alternative – making the OS flush data more often
is another, e.g. as Windows does (every
erally inverse of the boot order – if
a unit has "After=X", it will be started after X, but stopped before X. So
your unit should have a Requires= (or Wants=) plus an After= for every
service it actually needs.
Also – the unit seems more like a Type=oneshot, not a Type=simple.
--
Mant
On Thu, Sep 24, 2015, 09:40 Luca Bertoncello
wrote:
> Hi Lennart,
>
> thank you for your answer!
>
> > There is no concept of "first" or "last" in systemd, since it's not
> clear what
> > that's supposed to mean if there are multiple, and what happens if some
> > operation results in activation?
led from one of those distros?
>
udisks v1 used to do that by default, and is still installed in some
places. (e.g. udiskie probably still depends on it?)
udisks v2 also has an option (controlled through an udev property,
ENV{UDISKS_FILESYSTEM_SHARED}) to do the same.
--
var/lib/upower)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
I wonder if this could be handled with a generic Type=oneshot,
ExecStart=driverctl bind foo...
--
Mantas Mikulėnas
On Sep 28, 2015 21:48, "Flavio Leitner" wrote:
> On Mon, Sep 28, 2015 at 08:06:50PM +0200, Kay Sievers wrote:
> > On Sun, Sep 27, 2015 at 11:37 PM, Flav
You normally shouldn't need to do this. For user bus, the address is
configured in dbus.socket; for session buses it is passed as command line
option.
On Sun, Oct 4, 2015, 21:40 arnaud gaboury wrote:
> As I am trying to improve my knowledges in how dbus work, I discovered
> this file in /etc/dbu
Also this is not the path used by most software, anyway; the user bus is
expected at %t/bus, not %t/user_bus_address. I think it was moved in v205
or v215.
On Mon, Oct 5, 2015, 07:03 Mantas Mikulėnas wrote:
> You normally shouldn't need to do this. For user bus, the address is
> co
ed system due it's footprint but I suspect that I should live
> with it. :-)
>
While I'm not really comfortable suggesting this, old polkit versions
(v0.105 and earlier) used a different rules format without JavaScript.
--
Mantas Mikulėnas
___
syst
use devel mailing list for such questions.
>
It's also a tech support list.
> If you want to install systemd on linux mint, you should do something like
> this:
> http://superuser.com/questions/917804/switching-to-systemd-on-linux-mint
It's Debian-specific; I&
find it.
>
Try `tig blame src/udev/ata_id/ata_id.c`, it follows renames and you can
jump to an older commit using , and back using <
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
nit files directly. For now, use directory
ACLs.
(Wonder if this could somehow make use of GNOME's new admin:/// vfs...)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
build-time option, which creates
problems when booting a non-SMACK kernel...
Any ideas on how to fix it? All previous such fixes were for API
filesystems in mount-setup.c and could do flexible checks, but that clearly
won't work for mount units.
--
Mantas
er.target
├─apache2.service
├─bind9.service
├─binfmt-support.service
├─cron.service
├─dbus.service
See also manual pages for bootup(7), systemd.unit(5)
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
; is kind of "path": connect to host "foo", enter its container "bar",
> and from there connect to "bar"'s container "baz" and then further
> down into "baz"'s container "waldo"... Containers are stackable after
On Fri, Oct 23, 2015 at 2:11 PM, Lennart Poettering
wrote:
> On Fri, 23.10.15 14:03, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
> > On Fri, Oct 23, 2015 at 1:55 PM, Lennart Poettering <
> lenn...@poettering.net>
> > wrote:
> >
> > > On
ependencies local-fs.target
local-fs.target
● ├─boot.mount
● ├─home.mount
● ├─tmp.mount
● └─var-lib-machines.mount
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
d.d uses the exact same locations and configuration as kmod &
modprobe:
http://man7.org/linux/man-pages/man8/modprobe.8.html
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
but yet another variable.
>
There is no such option in systemd. If you need shellscript-like features,
just run a wrapper shell script via ExecStart.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
ted by journal-remote (where the
admin might want to keep it for archival purposes), and so on.
Therefore journald will not delete journals with other machine-ids, since
doing so would possibly apply two conflicting policies to the same logs –
yours, and the container's/client's.
--
Ma
#!/bin/sh
> # Approach cribbed from http://www.opopop.net/Harnessing_DBus/
Might as well use ctypes.sh then... Or a more capable language:
https://gist.github.com/grawity/a10ee46d7ff58048d483
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
reedesktop.org/wiki/Software/systemd/hostnamed/
and so on.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
orted as kvm, and any other qemu
> as qemu.
>
As I understand it, VirtualBox doesn't use KVM as *backend*; it only
exposes a KVM-like paravirt interface to *guests*.
--
Mantas Mikulėnas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
701 - 800 of 1190 matches
Mail list logo
