On Thu, 20 Aug 2015 03:26:21 +0800
Tom Yan tom.t...@gmail.com wrote:
Woo it's a win of almighty grawity again! \o/
My rules works perfectly fine with the 70- prefix just as the shipped
70-uaccess.rules. Should have thought about it. Any pointer for
details about the consumed here btw?
Well, as in the paste earlier, 73-seat-late.rules is the place where udev
actually looks at the uaccess tag and applies initial ACLs on device
connect. So all devices must be properly tagged before they reach that rule.
(Logind /also/ looks at the uaccess tag and applies ACLs independently of
Systemd conference presentation proposal.
Title: Systemd and self-introspection.
Systemd poll results (Distrowatch.com, Jul 2015):
I use systemd and like it:787 (30%)
I use systemd and dislike it:318 (12%)
I am not using systemd and
On 08/21/2015 03:44 AM, he...@andreborie.name wrote:
Hello,
I'm trying to use systemd-networkd to manage a sit tunnel and I've hit
problem. My internet connection is provided by ppp0 which isn't
directly managed by networkd and can come and go at anytime. I have a
.network file with [Match]
On Thu, 20.08.15 23:41, Michael Biebl (mbi...@gmail.com) wrote:
Hi,
say I wanted to grant an unprivileged userA the ability to
systemctl start/stop/restart/reload foo.service
and only grant this for foo.service.
Is there a way to achieve that without resorting to using hacks like
sudo
Hello,
I'm trying to use systemd-networkd to manage a sit tunnel and I've hit
problem. My internet connection is provided by ppp0 which isn't
directly managed by networkd and can come and go at anytime. I have a
.network file with [Match] Name=ppp0 that works as expected and
correctly
https://github.com/systemd/systemd/pull/998 unless you want to bubble this
all the way up to the commandline.
On Tue, Aug 18, 2015 at 4:31 PM, Vincent Batts vba...@redhat.com wrote:
On Tue, Aug 18, 2015 at 12:29 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 18.08.15
Hi,
say I wanted to grant an unprivileged userA the ability to
systemctl start/stop/restart/reload foo.service
and only grant this for foo.service.
Is there a way to achieve that without resorting to using hacks like
sudo or a suid binary? From a cursory look, the existing PolicyKit
rules are
Ah that explains everything. I was just confused about
RUN{builtin}+=uaccess but now I get it. Thanks a lot!
On 20 August 2015 at 18:05, Mantas Mikulėnas graw...@gmail.com wrote:
Well, as in the paste earlier, 73-seat-late.rules is the place where udev
actually looks at the uaccess tag and
On Sun, Aug 16, 2015 at 9:29 AM, Lennart Poettering
lenn...@poettering.net wrote:
Could you file a github RFE issue, asking for support for watchdog
keep-alive message send stuff in PID 1 and nspawn, and watchdog
keep-alive message receive stuff in nspawn? I think it would make a
lot of sense
10 matches
Mail list logo
