Hi All,
Any inputs on this?
--
Shedi
On Mon, Apr 15, 2024 at 7:15 PM Shreenidhi Shedi <
shreenidhi.sh...@broadcom.com> wrote:
> Hi All,
>
> I'm trying to use volatile root feature for the first time.
>
> This is my /etc/fstab:
> ```
> #system mnt-pt type options du
Hi All,
I'm trying to use volatile root feature for the first time.
This is my /etc/fstab:
```
#system mnt-pt type options dump fsck
PARTUUID=ad7ab716-2c0a-4dbe-9a28-06dc8bd0383b / ext4
defaults,barrier,noatime,data=ordered 1 1
```
And systemd grub configs are:
systemd_cmdline=net.ifnames=0
Hi All,
I tried this on Fedora 39 so anyone can reproduce this at their end I guess.
Steps:
1. systemctl restart dbus
2. Try to start a new ssh session or invoke a reboot command
It will take 25 seconds to finish and if we restart systemd-logind, system
becomes stable. busctl --list shows
On Thu, Mar 7, 2024 at 1:24 PM Shreenidhi Shedi <
shreenidhi.sh...@broadcom.com> wrote:
> On Wed, Mar 6, 2024 at 8:57 PM Lennart Poettering
> wrote:
>
>> On Mi, 06.03.24 14:44, Shreenidhi Shedi (shreenidhi.sh...@broadcom.com)
>> wrote:
>>
>> > > Lenn
On Wed, Mar 6, 2024 at 8:57 PM Lennart Poettering
wrote:
> On Mi, 06.03.24 14:44, Shreenidhi Shedi (shreenidhi.sh...@broadcom.com)
> wrote:
>
> > > Lennart Poettering, Berlin
> >
> > Thanks a lot for the responses Andrei, Poettering .
> > We took i
On Wed, Mar 6, 2024 at 2:01 PM Lennart Poettering
wrote:
> On Mi, 06.03.24 11:11, Shreenidhi Shedi (shreenidhi.sh...@broadcom.com)
> wrote:
>
> > Hi All,
> >
> > What is the rationale behind using sshd.socket other than not keeping
> sshd
> > daemon running al
Hi All,
What is the rationale behind using sshd.socket other than not keeping sshd
daemon running always and reducing memory consumption?
With sshd.socket, systemd does a fork/exec on each connection which is
expensive and with the sshd.service approach server will just connect with
the client
