$HOME help?
Benjamin Godfrey replied:
Perhaps, I don't understand your objection. Maybe, you are concerned about
a scenario wherein the situation below is true, i.e. there is an open fd in
the $HOME directory keeping the directory open for an active process, and
another fd is added by yet
Lennart Poettering, wrote:
I think we probably should change systemd-logind to
implicitly and unconditionally keep an open fd to the home dir of a
user around as long as there's at least one session of them around,
simply to make clear that sessions keep home dirs busy. This, as side
effect would
ion where delay is
fixing the bootup hang problem.
If i add debug logs in systemd or enable dracut logs also issue is not
seen , i.e boot up is not hung.
>
> Benjamin Godfrey
In the unit file, TimeoutSec is different from TimeoutStartSec The
default is 60s. Try changing the number to 61
k -C -f /dev/sda1'" would mean the fsck
command is executing.
Something like "Command '/sbin/fsck -C -f /dev/sda1' took 10 seconds to
execute" might help you find the issue.
Benjamin Godfrey
On Tue, May 9, 2023 at 5:00 AM
wrote:
> Send systemd-devel mailing li
usr/bin/systemd-run --scope
--rootimage=/path/to/root/image --extensionimages=/path/to/extension/image
/usr/bin/my-command
[Install] WantedBy=multi-user.target
Benjamin Godfrey
On Fri, May 5, 2023 at 5:00 AM
wrote:
> Send systemd-devel mailing list submissions to
> [email protected]
u working on a Chromebook.
Is it really that much more complicated to complete the boot process in
chroot?I'll try the container solution.
yours truly,
Benjamin Godfrey
On Wed, Apr 26, 2023 at 5:00 AM
wrote:
> Send systemd-devel mailing list submissions to
> systemd-dev
leshoot this issue?
Thank you for your time.
yours truly,
Benjamin Godfrey
