Package Details: systemd-guest-user 33.2-1

Git Clone URL: https://aur.archlinux.org/systemd-guest-user.git (read-only, click to copy)
Package Base: systemd-guest-user
Description: A simple systemd configurations for guest user support
Upstream URL: https://github.com/Akrai/systemd-guest-user
Keywords: guest systemd user
Licenses: GPL3
Submitter: pavelshuvalov
Maintainer: akrai
Last Packager: akrai
Votes: 11
Popularity: 0.014785
First Submitted: 2016-10-14 12:39 (UTC)
Last Updated: 2019-11-04 16:25 (UTC)

Required by (0)

Sources (1)

Pinned Comments

akrai commented on 2018-08-01 14:49 (UTC) (edited on 2019-11-04 16:11 (UTC) by akrai)

Installing the package gets your system ready to use the guest user, which is basically a normal user with a tmpfs home folder (which gets erased after every reboot, not after a logout), but please notice two things:

  1. You probably want to add the guest user to some system groups you may consider in order to be able to use some resources of your computer, the same way as any other human user

  2. The script copies any file placed in the /etc/skel/ folder to the guest home after every reboot, intended mainly for copying config files you may consider useful to copy in every new guest session, for example if you need special graphical or network config files placed in order to get a properly working guest user. Any suggestion is welcomed

Latest Comments

1 2 3 4 5 6 7 Next › Last »

akrai commented on 2020-10-01 13:07 (UTC)

Or just change manually the id after installing the package:

https://www.cyberciti.biz/faq/linux-change-user-group-uid-gid-for-all-owned-files/

As setting a fixed UID in the preinstall script could, potentially, encounter a conflict for someone as the id has been already taken (very unlikely, but still posible, for example there is another package in AUR that creates a user with the ID 999 too), and as setting an UID < 1000 is not needed by almost anyone, I prefer that those that wants it to be < 1000 change it manually after the install, which is just a few commands. Also, if you want this procedure to be automatic for production (installing guest user for a lot of machines and also setting UID < 1000) then you can just compile the package, and edit the systemd-guest-user.install file to just set manually there the UID in the useradd command, as you said

akrai commented on 2020-10-01 08:29 (UTC)

I prefer to not do it

https://unix.stackexchange.com/questions/343445/user-id-less-than-1000-on-centos-7

But you can edit the package yourself to make that simple change, just compile the package and replace the content of the compressed file

librewish commented on 2020-10-01 02:20 (UTC)

@akrai

We need to change uid to something below 1000

For ex useradd -u 999 -c Guest guest

In the systemd-guest-user.service

Can you make this change.

akrai commented on 2020-07-12 18:38 (UTC)

As I said I'm not a systemd expert, I didn't created the config files, I just created the AUR package and forked the repo in github as the original creator dropped the repo and the AUR package. But still, I can make some research and make some basic edits. As I know, ConditionUser would mean that the unit would only run if the specified user is logged in, which is NOT what we want. What would happen if you log out without rebooting? It would delete the tmpfs. Right now you can log out and the files are still there until you reboot, which I prefer because, for me, logging out instead of rebooting would mean a somewhat high chance of making a mistake, I mean, it would probably mean, at least for me, that i tried to change user without wanting to delete the files and i used the wrong button

I don't know, and besides, using that condition may probably have to reconsider the design of the rest of the units, which I'm not in the condition to do. The github is open to pull requests, if you have any commit i'm open to read it and accept it.

madjoe commented on 2020-07-12 16:05 (UTC)

I contacted systemd crew and they seem surprised how frequently this service runs - successfully 5 times in 2 seconds? It's failing because it's restarting too often. There's nothing in the unit actually failing. They believe it's broken by design. Besides, why this wouldn't be a user unit with ConditionUser=guest? According to them, systemd-guest-user.service should be a sysusers.d fragment that makes a group and a user with a fixed UID/GID: https://0x0.st/itwc.txt

Removing this package for now...

akrai commented on 2020-07-11 10:24 (UTC)

as i said i'm not a systemd expert, try to look at the journal of those units

madjoe commented on 2020-07-10 23:13 (UTC)

@Akrai: Where should I look, could you give me some pointers, please?

akrai commented on 2020-07-10 13:48 (UTC)

okay i'm not a systemd expert but i'm pretty sure either Requires or After is the line that makes the service start after the content of any of those two have started. So that would mean in your case that the unit that triggers the start of systemd-guest-config.service is restarting several times for some reason, which probably shouldn't be restarting. In my case, for example, there is no problem with systemd-guest-config

madjoe commented on 2020-07-10 13:40 (UTC)

systemd-guest-config.service starts/finishes multiple times on reboot/shutdown.

I just installed systemd-guest-user from AUR and now I could see "FAILED: Failed to start systemd-guest-config.service." 3x in a row every time I reboot, or shutdown.

Here's the output of journalctl -u systemd-guest-config.service: https://hastebin.com/radohorege.sql

librewish commented on 2019-11-04 16:20 (UTC)

yes remove it. as /etc/skel is always there. so no need to create it

1 2 3 4 5 6 7 Next › Last »