n't even
mention the "70-steam-input.rules" file.
I did try to just rename "70-steam-input.rules" to be sure it is
responsible for the "uaccess" tag to be set and it is. If the file is
renamed, then I no longer get unwanted write permissions.
Can someone please
Session 8 of user kodi.
This scope does not have my memory limitation enabled. How to get this
setting in there?
On 3/16/19 6:02 PM, Manuel Reimer wrote:
Hello,
I'm using this service file:
https://github.com/VDR4Arch/vdr4arch/blob/master/kodi-standalone-service/kodi.service
Hello,
I'm using this service file:
https://github.com/VDR4Arch/vdr4arch/blob/master/kodi-standalone-service/kodi.service
Resulting in this status:
# systemctl status kodi
● kodi.service - Starts instance of Kodi using xinit
Loaded: loaded (/usr/lib/systemd/system/kodi.service; enabled;
Hello,
can someone please give a short hint or link to easy to understand
information, so I can find the difference between the "Capability"
settings in systemd.exec?
I have two situations:
What will I use if I have a "User=" configured, but I want to give one
or two additional
Hello,
my distributor sets the following rule in /usr/lib/udev/rules.d:
KERNEL=="uinput", SUBSYSTEM=="misc", OPTIONS+="static_node=uinput",
TAG+="uaccess"
I think this is not a good idea and that there is a good reason why
users can't create uinput devices, so I want to get rid of that
Hello,
I want to create a daemon which translates inputs, given by an game
controller (/dev/input/eventX). The default is, that the tag "uaccess"
is set there.
As soon as my daemon runs, I don't want to use the original input
device. Other applications should not connect to the original
On 09/21/2015 07:39 PM, David Herrmann wrote:
Why do you use networkd at all? Just disable it via `systemctl disable
systemd-networkd`.
I thought it could be a good idea to use networkd for the initial
configuration so network mask and static IP is set up on boot.
Regards,
Manuel
Hello,
it seems to be impossible to just stop networkd (keeps starting itself
again).
If I use "ifconfig" to turn off one NIC, then networkd immediately
restarts it.
What do I have to do to gain back control over my network interfaces? I
want to be able to turn off one interface.
Thanks
Hello,
if I run the following code on an intel based platform, then I don't
have any problems:
use Net::DBus;
my $bus = Net::DBus->system();
my $logind = $bus->get_service('org.freedesktop.timedate1');
my $manager = $logind->get_object('/org/freedesktop/timedate1',
Hello,
I want to run systemd on a embedded linux board. I have connected a RTC
module via I2C.
What I want to do is to set the time via hwclock --hctosys during boot. I
have to do this before the first systemd-timer is triggered.
How do I have to create my service-file to set the time as early
Mantas Mikulėnas grawity at gmail.com writes:
Doesn't the kernel already do the same via CONFIG_RTC_HCTOSYS_DEVICE?
The kernel reads from /dev/rtc0 which is the CPU built-in RTC (iMX233). My
added RTC has to be registered first and then appears as /dev/rtc1.
Greetings,
Manuel
Lukasz Skalski l.skalski at samsung.com writes:
You can define which RTC (/dev/rtcX) should be read -
(rtc1) RTC used to set the system time option in kernel menuconfig.
Yes, this is possible. But my RTC does not exist until I do the following on
shell:
echo ds1307 0x68
On 04/28/2014 05:47 PM, Lennart Poettering wrote:
Why do you have two RTCs even enabled? What's the logic there? And why
isn't rtc0 just fine? If it doesn't work, why have it enabled at all?
rtc0 is part of the CPU (iMX233) and only works if a LiPo battery is
connected. I prefer a RTC chip
On 02/18/2014 11:05 AM, Thomas Bächler wrote:
Am 17.02.2014 21:27, schrieb Manuel Reimer:
As soon as a bigger coredump (about 500 MB) is to be stored, the whole
system slows down significantly. Seems like storing such big amounts of
data takes pretty long and is a very CPU hungry process...
I
Hello,
if a bigger application crashes with coredump, then systemd-coredump
seems to have a few problems with that.
At first, there is the 767 MB limitation which just drops all bigger
coredumps.
But even below this limit it seems to be impossible to store coredumps.
I did a few tries and
Hello,
I'm using systemd on a small embedded board. As I have to run journalctl
anyway, my plan is to try to use it to collect logs, so I can transmit them
to a server once a day.
My plan is to do the following settings:
Storage=volatile
RuntimeMaxUse=2M
I only have 64MB and I don't want to
David Strauss david at davidstrauss.net writes:
Do you really need to clear it? Presumably, the system has to meet its
memory constraints just before you dump the logs. What is the
advantage of freeing memory that the system has to account for,
anyway?
Yes, that's right. Maybe I even reduce
David Strauss david at davidstrauss.net writes:
Instead of doing your own compressed dump to flash, how about this:
(1) Enable persistence.
(2) When you want a backup, force rotation by sending the journal SIGUSR2
(3) Copy away the rotated journal file and delete it.
This doesn't help
David Strauss david at davidstrauss.net writes:
You can store the last cursor you had in each dump (even in memory
somewhere) and tell journalctl to start from that the next time using
--after-cursor=.
Another option seems to be to store a timestamp in memory and use --since.
Maybe this is
to disable it permanently?
Thank you very much in advance
Greetings,
Manuel Reimer
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hello,
I need two service files for two daemons.
The first one expects some type of device to be accessible via USB.
So what I need for this one is something like Wait until all currently
plugged in USB devices are enumerated and the relevant kernel modules
have been loaded.
The second one
On 08/19/2013 04:53 PM, Greg KH wrote:
The second one wants to access DVB devices.
These could be connected via PCI, PCI express or USB. So here I need
Wait until all possible, currently connected, DVB devices are
initialized and drivers are loaded.
Same here, there is no way to ever do this
ignores the power button, first (and then reboot
his system, so logind.conf is interpreted, again).
Yours
Manuel Reimer
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hello,
I want to find out why inhibiting the power button doesn't work system wide.
As first step, I want to compare debug messages, logged by logind.
But unfortunately I don't manage to get them logged to somewhere. Enabling debug
output for systemd seems to not enable debug output for
...
For me it seems like something caused this whole thing to get broken. Can
someone reproduce or is this only broken on ArchLinux?
Yours
Manuel Reimer
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org
.
Seems like I'm seeing the same effect with my code, but as I want to use an
inhibitor in a daemon that gets started by systemd while the system boots, this
doesn't make much sense for me.
Manuel Reimer wrote:
Hello,
I'm using ArchLinux which currently uses systemd 198.
I try to inhibit
Hello,
I need a reliable way to find out if a system, where my software runs on, uses
systemd.
My first thought:
$ cat /proc/1/comm
systemd
Is this a reliable way that will also work in the next few releases of systemd,
or should I use something different?
Thanks in advance.
Yours
Mantas Mikulėnas wrote:
I would support this, partially. The ellipsized output is only useful
as a rough overview, but seeing such messages as session closed...ty
is very rarely actually helpful... The pager can stay, though.
It can stay, but my opinion is, that it shouldn't be the default.
Hello,
journalctl cuts longer log lines at some point. Is there a way to disable this?
Thanks in advance
Yours
Manuel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hello,
if I want a daemon to, for example listen for the power button, then there are
two possible solutions. Either configure systemd to not longer handle the power
button or register an inhibitor to make systemd stop handling the power button.
Is it good practice to use systemd-inhibit in
30 matches
Mail list logo
