On Nov 14 2020, Uoti Urpala wrote:
> On Sat, 2020-11-14 at 09:31 +0000, Nikolaus Rath wrote:
>> # journalctl --disk-usage
>> Archived and active journals take up 320.0M in the file system.
>>
>> # journalctl > alllogs
>> # ls -lh alllogs
>> -rw-r
On Nov 14 2020, Andrei Borzenkov wrote:
> 14.11.2020 14:32, Nikolaus Rath пишет:
> ...
>>>>
>>>> # grep -vE '^#' /etc/systemd/journald.conf
>>>>
>>>> [Journal]
>>>> SystemMaxUse=300M
>>>
>>> The num
On Nov 14 2020, Paul Menzel wrote:
>> I just discovered that on one of my systems journald only retains log
>> entries for about 10 days:
>>
>> # journalctl | head -1
>> -- Logs begin at Wed 2020-11-04 15:57:13 UTC, end at Sat 2020-11-14 09:28:19
>> UTC. --
>>
>> I do not understand what could ca
Hello,
I just discovered that on one of my systems journald only retains log
entries for about 10 days:
# journalctl | head -1
-- Logs begin at Wed 2020-11-04 15:57:13 UTC, end at Sat 2020-11-14 09:28:19
UTC. --
I do not understand what could cause this, because I have no retention
limit config
On Jul 02 2018, Lennart Poettering wrote:
>> Still not quite working, now there seems to be a problem with
>> /proc/self/fd in the new shell:
>>
>> $ sudo systemd-nspawn -M $MACHINE \
>> --private-users=1379532800:65536 --private-network \
>> --as-pid2
[...]
>>
>> What's happening here
On Jun 25 2018, Lennart Poettering wrote:
> On Sa, 23.06.18 21:57, Nikolaus Rath (nikol...@rath.org) wrote:
>
>> On Jun 23 2018, Nikolaus Rath wrote:
>> > On Jun 23 2018, aleivag wrote:
>> >> short answer, yes, `machinectl login` is only suppported fo
On Jun 26 2018, Lennart Poettering wrote:
> On Di, 26.06.18 09:39, Nikolaus Rath (nikol...@rath.org) wrote:
>
>> Hi,
>>
>> That makes sense.. but is there any way to find out *globally* what
>> devices are mounted in *any* namespace?
>
> If you a PID
Hello,
I'm maintainer of libfuse. libfuse ships with a SysV init script[1] that
I'd like to replace with a systemd unit file. It currently does just two
things:
1. loads fuse kernel module
2. mounts fusectl filesystem at /sys/fs/fuse/connections
I don't think there is a need to retain the functi
it. If you need to access the
> data, you can use machinectl:
> https://www.freedesktop.org/software/systemd/man/machinectl.html
>
>
> On June 23, 2018 8:49:01 AM Nikolaus Rath wrote:
>
>> Hi,
>>
>> I have just started using machinectl and systemd-nspawn and
On Jun 25 2018, Lennart Poettering wrote:
> On Sa, 23.06.18 14:42, Nikolaus Rath (nikol...@rath.org) wrote:
>
>> Hello,
>>
>> When running systemd-nspawn with --private-network, I am getting mount
>> errors:
>>
>> # systemd-nspawn -M iofabric
On Jun 23 2018, Nikolaus Rath wrote:
> On Jun 23 2018, aleivag wrote:
>> short answer, yes, `machinectl login` is only suppported for systemd-init ,
>> and `machinectl shell` `systemd-run` will try to talk to the container via
>> dbus, so i dont think you are force to have
On Jun 23 2018, aleivag wrote:
> short answer, yes, `machinectl login` is only suppported for systemd-init ,
> and `machinectl shell` `systemd-run` will try to talk to the container via
> dbus, so i dont think you are force to have systemd runing inside the
> container (i may be wrong) but you do
Hi,
On Sat, 23 Jun 2018, at 15:31, Vito Caputo wrote:
> On Sat, Jun 23, 2018 at 03:09:04PM +0100, Nikolaus Rath wrote:
> > How would I go about starting an additional shell in an existing
> > container? I am starting the container with:
> >
> > $ systemd-nspawn -M
Hello,
How would I go about starting an additional shell in an existing
container? I am starting the container with:
$ systemd-nspawn -M foo --as-pid2 --register=no
"foo" is a raw image retrieved with machinectl. If I simply execute the
above command again, I am getting a "Disk image
/var/lib/ma
Hi,
I have just started using machinectl and systemd-nspawn and like it a
lot. However, there is one thing that I could not figure out from the
documentation and not knowing it makes me feel uncomfortable: where
exactly is the root filesystem for the container mounted, and how can I
access it from
Hello,
When running systemd-nspawn with --private-network, I am getting mount
errors:
# systemd-nspawn -M iofabric --as-pid2 --private-users=1379532800:65536
--register=no --private-network
Spawning container iofabric on /var/lib/machines/iofabric.raw.
Press ^] three times within 1s to kill cont
On Jun 14 2016, Mantas Mikulėnas wrote:
> On Tue, Jun 14, 2016 at 9:16 PM, Nikolaus Rath wrote:
>
>> Hello,
>>
>> Are there any best practices for adjusting values in /proc on system
>> boot? Specifically, I'm looking for a way to do
>>
Hello,
Are there any best practices for adjusting values in /proc on system
boot? Specifically, I'm looking for a way to do
echo 1 > /proc/sys/kernel/safename/mode_for_unprivileged
echo 1 > /proc/sys/kernel/safename/mode_for_privileged
..as soon as possible when booting.
I think this fil
Hello,
Is there a way to run systemd-analyze for system shutdown, instead of
boot-up?
I am pretty sure that my system takes way longer than it should to power
off, but the "shutdown-log.txt" technique from
https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
doesn't show anything obv
On Apr 16 2015, Lennart Poettering wrote:
> On Wed, 15.04.15 22:45, Nikolaus Rath (nikol...@rath.org) wrote:
>> I don't quite understand this:
>>
>> $ systemctl --user status autocommit-org.service
>> ● autocommit-org.service - Auto-commits changes to org
Hello,
I don't quite understand this:
$ systemctl --user status autocommit-org.service
● autocommit-org.service - Auto-commits changes to orgmode files.
Loaded: loaded (/home/nikratio/.config/systemd/user/autocommit-org.service;
static)
Active: inactive (dead) since Wed 2015-04-15 22:42:1
Mantas Mikulėnas writes:
> On Wed, Nov 26, 2014 at 11:06 PM, Nikolaus Rath wrote:
>
>> Hello,
>>
>> I'd like to start a unit on system shutdown and reboot, but do so
>> immediately after the "systemctl reboot" command is executed, before any
>>
Mantas Mikulėnas writes:
> On Wed, Nov 26, 2014 at 11:06 PM, Nikolaus Rath wrote:
>
>> Hello,
>>
>> I'd like to start a unit on system shutdown and reboot, but do so
>> immediately after the "systemctl reboot" command is executed, before any
>&g
Hello,
I'd like to start a unit on system shutdown and reboot, but do so
immediately after the "systemctl reboot" command is executed, before any
other units are terminated.
Is there a way to do that?
At first I thought that Before=shutdown.target might work, but thinking
about it, I think this
Nikolaus Rath writes:
> On 11/13/2014 12:54 PM, Nikolaus Rath wrote:
>> Nikolaus Rath writes:
>>> Lennart Poettering writes:
>>>> On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote:
>>>>
>>>>>> Please boot with "syst
Nikolaus Rath writes:
> On 11/13/2014 12:54 PM, Nikolaus Rath wrote:
>> Nikolaus Rath writes:
>>> Lennart Poettering writes:
>>>> On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote:
>>>>
>>>>>> Please boot with "syst
Hello,
My journal gets corrupted on pretty much a daily basis. I typically
notice this because things like "systemctl -n 3" take ages to run. When
I then run "journalctl --verify", I get output like this:
Invalid data object at hash entry 3944 of 233016░░░ 49%
File corruption det
On 11/13/2014 12:54 PM, Nikolaus Rath wrote:
> Nikolaus Rath writes:
>> Lennart Poettering writes:
>>> On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote:
>>>
>>>>> Please boot with "systemd.log_level=debug", then make the mach
Nikolaus Rath writes:
> Lennart Poettering writes:
>> On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote:
>>
>>> > Please boot with "systemd.log_level=debug", then make the machine hang
>>> > and check what the last things in th
Lennart Poettering writes:
> On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote:
>
>> > Please boot with "systemd.log_level=debug", then make the machine hang
>> > and check what the last things in the logs say. Maybe then paste that
>> >
Lennart Poettering writes:
> On Thu, 06.11.14 19:07, Nikolaus Rath (nikol...@rath.org) wrote:
>
>> Hello,
>>
>> I'm having some trouble shutting down my system with systemd. What
>> happens is the following:
>>
>> * If I execute &q
Hello,
I'm having some trouble shutting down my system with systemd. What
happens is the following:
* If I execute "systemctl reboot" while a text console is active,
everything works fine.
* If I execute "systemctl reboot" while the X11 console is active, the
system hangs (I tried waitin
Lennart Poettering writes:
>>> systemd will invoke /bin/mount when mounting a file system, and
>>> /bin/umount when unmountin it. fuse file systems may fork off background
>>> processes from there, that will be kept around while the file system is
>>> mounted, and terminated atfer the file system
Lennart Poettering writes:
> On Mon, 21.04.14 19:05, Diogo Vieira (d...@eurotux.com) wrote:
>
>> Hello,
>>
>> I'm trying to create a unit to automatically mount a fuse filesystem
>> known as S3QL, which is the one in question in this older thread:
>> http://lists.freedesktop.org/archives/systemd-
Matthew Monaco writes:
> On 04/19/2014 02:49 PM, Nikolaus Rath wrote:
>> I have several LUKS encrypted volumes that use the same
>> passphrase. Before switching to systemd, I have used the decrypt_keyctl
>> keyscript to cache the passphrase, so that I have to enter it only o
Hello,
I have several LUKS encrypted volumes that use the same
passphrase. Before switching to systemd, I have used the decrypt_keyctl
keyscript to cache the passphrase, so that I have to enter it only once.
As far as I can tell, the systemd cryptsetup generator is ignoring the
keyscript option i
On 12/13/2012 06:58 PM, Andrey Borzenkov wrote:
> В Thu, 13 Dec 2012 15:35:11 -0800
> Nikolaus Rath пишет:
>
>> On 12/13/2012 08:35 AM, Andrey Borzenkov wrote:
>>
>> Now, I could add the missing rule and program to the initrd, but I feel
>> this is really open
On 12/13/2012 08:35 AM, Andrey Borzenkov wrote:
> В Mon, 10 Dec 2012 11:03:54 -0800
> Nikolaus Rath пишет:
>
>> Hello,
>>
>> I have created a udev rule to set the owner of a specific block device:
>>
>> SU
On 12/11/2012 09:47 AM, Colin Guthrie wrote:
> 'Twas brillig, and Nikolaus Rath at 11/12/12 16:31 did gyre and gimble:
>> On 12/11/2012 03:00 AM, Colin Guthrie wrote:
>>> 'Twas brillig, and Nikolaus Rath at 10/12/12 19:03 did gyre and gimble:
>>>> Hello,
>
On 12/11/2012 03:00 AM, Colin Guthrie wrote:
> 'Twas brillig, and Nikolaus Rath at 10/12/12 19:03 did gyre and gimble:
>> Hello,
>>
>> I have created a udev rule to set the owner of a specific block device:
>>
>> SUB
Hello,
I have created a udev rule to set the owner of a specific block device:
SUBSYSTEM=="block",
ENV{DM_UUID}=="LVM-yYuoI8k05GWxZnz9BeEIwPUGGeojzF3dZZmXTYRqC051Tllj76OHdDlzYhKZUu7u",
OWNER="1000"
If I disable and re-enable this logical volume with lvchange, it gets
created with the correct own
Stef Bon writes:
> That's why I advise to use a pidfile systemd can watch.
I believe one of systemd's design goals is to actually get rid of pid
files and related hacks. If I want to use systemd with a pidfile, I may
just as well use systemd's sysvinit compatibility layer and stick with
my tradit
On 05/02/2012 03:53 PM, Lennart Poettering wrote:
> On Sat, 28.04.12 20:41, Nikolaus Rath (nikol...@rath.org) wrote:
>
>> Hello,
>>
>> I am struggling to come up with the correct way to define a unit
>> configuration for a FUSE based network file system.
>>
&g
Hello,
I am struggling to come up with the correct way to define a unit
configuration for a FUSE based network file system.
Generally, the file system needs to be mounted and unmounted with its
own programs (rather than with mount and umount). The main reason for
the custom umount command, howeve
44 matches
Mail list logo
