Am 23.08.20 um 19:19 schrieb Tom Browder:
> There is no official Apache systemd setup for Apache from source, and
> I didn't get any help from users there. I tried to mimic a good
> solution by first installing Apache with the Debian package and
> finding all the systemd files with "httpd" or
On Sun, Aug 23, 2020 at 12:36 PM Tomasz Torcz wrote:
>
...
> First of all, you got correct installation by installing distribution
> package. You can stop there.
> If you want to do the work, anyway, do the following:
> – read man systemd.unit, systemd.service, maybe some systemd tutorials
On Sun, Aug 23, 2020 at 12:19:15PM -0500, Tom Browder wrote:
> There is no official Apache systemd setup for Apache from source, and
> I didn't get any help from users there. I tried to mimic a good
> solution by first installing Apache with the Debian package and
> finding all the systemd files
Am So., 23. Aug. 2020 um 19:20 Uhr schrieb Tom Browder :
> I assume the data are correct, and I'm pretty sure there is some
> fancy, automated sysstemctl way to get it all working. I would
> greatly appreciate some guidance as to how to install the files
> correctly.
Those files are installed
There is no official Apache systemd setup for Apache from source, and
I didn't get any help from users there. I tried to mimic a good
solution by first installing Apache with the Debian package and
finding all the systemd files with "httpd" or "apache" in the name.
That resulted in the following
> Here is the log after authentication attempt:
> https://gitlab.com/-/snippets/2007113
> And just in case here is the full log since boot:
> https://gitlab.com/-/snippets/2007112
Sorry, links are broken, re-uploaded:
Authentication part: https://gitlab.com/-/snippets/2007123
Full log:
> As far as I can tell if discards are disabled, systemd tries to allocate
> full size of backing file. It is possible that there is simply not
> enough space to ensure full 400G (i.e. available space it consumed by
> something else). Are there are snapshots
Sorry, I think I lack some
That works! Thanks so much for the quick response.
I still feel it's a bit unintuitive though. I did find multiple open
issues asking for inhibitors that work with root as well. I think that
would be necessary for an intuitive solution.
Ideally, the following unit file would work:
```
[Unit]
Hi,
you can use Wants= to pull in another service, and then use
StopWhenUnneeded= to make that shutdown after the last sshd@.service
disappears.
So, I guess something like the below:
sshd@.service drop-in:
```
[Unit]
Wants=sshd-running.service
```
sshd-running.service
```
[Unit]
Nvm, that wouldn't work at all because inhibitor locks are ignored if
the user is privileged enough.
So getting the system to shut down after an sshd instance exits is
easy enough with SuccessAction. Waiting for all sshd instances to
finish before shutting down turns out to be extremely hard.
Hi,
After following
http://0pointer.de/blog/projects/socket-activated-containers.html
which details how to set up a socket activated container, I'm looking
into ways to have the container automatically shut down when the last
ssh connection terminates.
My idea was to have each sshd instance take
23.08.2020 15:34, Andrii Zymohliad пишет:
>> Here is the log after authentication attempt:
>> https://gitlab.com/-/snippets/2007113
>> And just in case here is the full log since boot:
>> https://gitlab.com/-/snippets/2007112
>
> Sorry, links are broken, re-uploaded:
>
> Authentication part:
Hello! I've lost the ability to log in to my systemd-homed user account. I
would be very grateful for any help!
If I log in as root and try to authenticate:
# homectl authenticate azymohliad
Then after typing my password I get the following output:
Operation on home azymohliad failed: Not
23.08.2020 09:34, Andrii Zymohliad пишет:
> Hello! I've lost the ability to log in to my systemd-homed user account. I
> would be very grateful for any help!
>
> If I log in as root and try to authenticate:
>
> # homectl authenticate azymohliad
>
> Then after typing my password I get the
14 matches
Mail list logo