Skip to content

lightdm: Add patch to avoid triggering home mounts. #2686

Merged
merged 1 commit into from
May 31, 2022
Merged

lightdm: Add patch to avoid triggering home mounts. #2686

merged 1 commit into from
May 31, 2022

Conversation

donald
Copy link
Collaborator

@donald donald commented May 31, 2022

As we have our homes on nfs, we don't want lightdm to search for icon
files in the homes.

Note, that the code, were lightdm enumerates the users and searches for
icon files in the users homess, is not used in the normal case. It is
only used when lightdm fails to get the service from accounts-service.

We've had the situation on one system, were accounts-service failed to
start in 30 seconds for unknown reassons after which gdm timed out and
used its own code, thereby mounting all nfs homes. Because of the notify
installed by the users filebrowser, these mounts even persisted.

It is yet unclear, why accounts-service needed ca 32 sesconds to start.
It was a special situation after a power failure on the campus which
resulted in a disconnect network in that building.

Anyway, if lightdm goes into the fallback mode for whatever reason, we
don't want it to walk over all homes.

Add patch.

Copy link
Collaborator

@wwwutz wwwutz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe put patch in beehive. anyway: LGTM

lightdm.be0 Outdated Show resolved Hide resolved
@pmenzel
Copy link
Collaborator

pmenzel commented May 31, 2022

Maybe AccountsService spend the time reading wtmp?

@pmenzel
Copy link
Collaborator

pmenzel commented May 31, 2022

I reported the issue upstream: https://github.com/canonical/lightdm/issues/254

As we have our homes on nfs, we don't want lightdm to search for icon
files in the homes.

Note, that the code, were lightdm enumerates the users and searches for
icon files in the users homess, is not used in the normal case. It is
only used when lightdm fails to get the service from accounts-service.

We've had the situation on one system, were accounts-service failed to
start in 30 seconds for unknown reassons after which gdm timed out and
used its own code, thereby mounting all nfs homes. Because of the notify
installed by the users filebrowser, these mounts even persisted.

It is yet unclear, why accounts-service needed ca 32 sesconds to start.
It was a special situation after a power failure on the campus which
resulted in a disconnect network in that building.

Anyway, if lightdm goes into the fallback mode for whatever reason, we
don't want it to walk over all homes.

Add patch.
@donald
Copy link
Collaborator Author

donald commented May 31, 2022

maybe put patch in beehive.

Done

@donald
Copy link
Collaborator Author

donald commented May 31, 2022

I reported the issue upstream: https://github.com/canonical/lightdm/issues/254

We can wait with this one for an answer.

Copy link
Collaborator

@pmenzel pmenzel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to wait for an answer, as I am not sure how actively lightdm is maintained and developed. I just wanted to document this.

@donald
Copy link
Collaborator Author

donald commented May 31, 2022

Hmmm. Github says "@pmenzel requested changes..." I resolved your review...

Copy link
Collaborator

@pmenzel pmenzel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now, I hit the right option.

@donald donald merged commit 8c7cb6e into master May 31, 2022
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants