Re: [systemd-devel] Upstreaming systemd patch
Hi, Not able to create pull request to systemd, permission denied to my github user credentials. I git cloned https://github.com/systemd/systemd While creating pull request, git push --set-upstream origin 1. Entered github username 2. Entered github passwd getting below error message for my github username. remote: Permission to systemd/systemd.git denied to fatal : unable to access 'https://github.com/systemd/systemd.git/': The requested URL returned error: 403 When tried to connect IRC channel irc://irc.freenode.org/systemd , it is giving error message "irc.freenode.org: Terminated". Please let me know to whom I need to connect with for getting pull request creation permission to systemd project. Thanks, Amit ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] nspawn file descriptor limit running without .service/nspawn file
Awesome, thanks! On Wed, Jul 29, 2020 at 9:05 PM Lennart Poettering wrote: > > On Mi, 29.07.20 20:08, Damian Ivanov (damianator...@gmail.com) wrote: > > > Hello, > > > > Hope you can help me with this. > > > > How do I set unlimited file descriptors for a systemd-nspawn container > > launcher via systemd-nspawn? > > > > I saw this for the service file > > LimitNOFILE=infinity > > > > found it from here > > https://github.com/systemd/systemd/issues/4997 > > > > Although I'm running it from cmd and > > --property="LimitNOFILE=infinity" gives me an error. > > > > Use > > systemd-nspawn --rlimit=RLIMIT_NOFILE=8192:16384 > > You get the idea. > > Lennart > > -- > Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] nspawn file descriptor limit running without .service/nspawn file
On Mi, 29.07.20 20:08, Damian Ivanov (damianator...@gmail.com) wrote: > Hello, > > Hope you can help me with this. > > How do I set unlimited file descriptors for a systemd-nspawn container > launcher via systemd-nspawn? > > I saw this for the service file > LimitNOFILE=infinity > > found it from here > https://github.com/systemd/systemd/issues/4997 > > Although I'm running it from cmd and > --property="LimitNOFILE=infinity" gives me an error. > Use systemd-nspawn --rlimit=RLIMIT_NOFILE=8192:16384 You get the idea. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] nspawn file descriptor limit running without .service/nspawn file
Hello, Hope you can help me with this. How do I set unlimited file descriptors for a systemd-nspawn container launcher via systemd-nspawn? I saw this for the service file LimitNOFILE=infinity found it from here https://github.com/systemd/systemd/issues/4997 Although I'm running it from cmd and --property="LimitNOFILE=infinity" gives me an error. Thanks for your help. Regards, Damian ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] 246 rc2 : stdio-bridge: failed to process bus
Since 246 i can't get -H to work anymore. It returns empty and on the host it logs Jul 29 17:18:05 agnus systemd-stdio-bridge[227915]: Failed to process bus: Operation not permitted PS: systemd-anaalyze completion does not cover log-level ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Creating a fake logind seat with no devices [Experiment]
On Mi, 29.07.20 00:11, nerdopolis (bluescreen_aven...@verizon.net) wrote: > Hi > > Sorry about the length. > > I have a unique thing I am trying to solve, is that if I have a service that > calls /sbin/logind under > something like tmux, and I set `Environment=XDG_SEAT=seat0` in the service > file, upon logging in, > pam_systemd fails to create a session, as it's seat0 and it's expecting a > valid TTY number, as it's > seat0. One of the side effects is that you lose the credential prompt that > you usually get if you > run a command like `systemctl restart foo.service`, and there could be other > things too? Seats are a concept of grouping hardware. A seat without hardware is pointless. If you have no hardware associated with a session then the session is seat-less, which is totally fine. I don't get what you are trying to do? Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd.timer every X days?
On 29/07/20 4:13 am, Ian Pilcher wrote: > On 7/28/20 11:07 AM, Mantas Mikulėnas wrote: >> I'd create a single raidcheck.service that runs daily and calls a >> script that itself determines which device to check, e.g. >> /dev/md$[dayofyear % 16]. > > That is the approach that I'm taking, although it means a fair bit of > work. I need to parse a configuration file, do a bunch of date-related > math, etc., as I don't really want to hard-code the number of RAID > devices into a C program. Why not just record which one you've just finished, then next time, read that and do the next in the sequence? Richard ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Creating a fake logind seat with no devices [Experiment]
Hi Sorry about the length. I have a unique thing I am trying to solve, is that if I have a service that calls /sbin/logind under something like tmux, and I set `Environment=XDG_SEAT=seat0` in the service file, upon logging in, pam_systemd fails to create a session, as it's seat0 and it's expecting a valid TTY number, as it's seat0. One of the side effects is that you lose the credential prompt that you usually get if you run a command like `systemctl restart foo.service`, and there could be other things too? On a QEMU multiseat system, if I instead say set `Environment=XDG_SEAT=seat-pci-pci-_00_04_0` pam_systemd works, as it's OK for non-seat0 to have a session with a TTY of 0, the (sd_pam) process runs, and privileged systemctl commands do the text mode prompts for authentication. The question is is that most systems are not going to have the hardware to create a second seat, as it seems that the only way to create a second seat is to have a hardware device tagged as master-of-seat in the second seat. Which is probably very rare. If I say set `Environment=XDG_SEAT=virtual` it fails because that seat doesn't exist. Is there a way to create a fake seat to start this service on? Or make an exception somehow to allow that session to not have to be on a 1-63 TTY? Or is it irrelevant as it's mostly for granting permissions to input and output devices? Although with out pam_systemd You do lose the text mode Authentication prompt for some systemctl commands, but I can't think of anything else. (except maybe that if your main session is playing sound, and then you switch and log into a TTY, you can hear the sound play again) - And in case if you need to know why I am asking this, for context, I am doing some experimenting with making a jerry-rigged vt experiment because of https://github.com/systemd/systemd/issues/15387 and https://bugzilla.kernel.org/show_bug.cgi?id=208239 It's just a collection of bash some scripts, and .service files that call an instance of tmux with lots of bindings turned off as root (which calls /sbin/login), grants a restricted system account access to the socket files, and then vte running under cage that runs as that account, and runs a tmux client that connects to the socket, but it's just an experiment. (And obviously needs kernel mode setting, although with those particular problems, I guess it will be irrelevant if you have no mode setting in the first place.) (Maybe I am going at this the wrong way, as both the Display Server session, and the guest session will BOTH need to be active, and that's not possible) Thanks ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
