Subject basically says it all. What's preventing us from supporting
this?
I'd personally appreciate being able to wire things up in my window
manager where I can run things via hotkeys like:
`systemd-run --machine finance --user firefox`
`systemd-run --machine entertainment --user firefox`
Am Montag, 11. März 2019 schrieb Lennart Poettering :
> On Do, 07.03.19 14:03, Marv Lelgemann (144db...@gmail.com) wrote:
>
>> I have a systemd service unit of type "dbus". I would like to have the
>> option to restart (or stop and start) the service with additional command
>> line arguments in
> On Mar 18, 2019, at 3:39 PM, Reindl Harald wrote:
>
>
>
> Am 18.03.19 um 20:23 schrieb Felipe Gasper:
>>> On Mar 18, 2019, at 2:54 PM, Reindl Harald wrote:
>>>
>>> Am 18.03.19 um 19:27 schrieb Felipe Gasper:
I’m noticing that ExecStop handlers execute not merely as a means for
Am 18.03.19 um 20:23 schrieb Felipe Gasper:
>> On Mar 18, 2019, at 2:54 PM, Reindl Harald wrote:
>>
>> Am 18.03.19 um 19:27 schrieb Felipe Gasper:
>>> I’m noticing that ExecStop handlers execute not merely as a means for
>>> systemd to stop a Service but also when that Service’s main
> On Mar 18, 2019, at 2:54 PM, Reindl Harald wrote:
>
>
>
> Am 18.03.19 um 19:27 schrieb Felipe Gasper:
>> I’m noticing that ExecStop handlers execute not merely as a means for
>> systemd to stop a Service but also when that Service’s main process receives
>> SIGTERM.
>>
>> The
Am 18.03.19 um 19:27 schrieb Felipe Gasper:
> I’m noticing that ExecStop handlers execute not merely as a means for
> systemd to stop a Service but also when that Service’s main process receives
> SIGTERM.
>
> The documentation (systemd.service) says that ExecStop commands are how
Am 18.03.19 um 11:31 schrieb Reindl Harald:
> Am 18.03.19 um 10:54 schrieb Lennart Poettering:
>> I am not fully grokking what you are trying to do, but to recv UDP
>> dgrams you'd have to write a tiny program that calls recvfrom() (or a
>> similar syscall) on the sockets passed, and then
On 2019-03-18 18:59, Lennart Poettering wrote:
I.e. a desktop system where user opens several browsers, with too many
tabs
with too many memory-intensive pages - becomes unresponsive for long
minutes, before OOM-killer finally kills the offender.
Quite frankly, this sounds like somehting
Am 18.03.19 um 10:54 schrieb Lennart Poettering:
> On Sa, 16.03.19 05:52, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>> Hi
>>
>> for a firewall development setup (nested virtualization) i have running
>> a tcp service like below on a VM liesting on a complete /24 network
>> behind a NAT
>>
On Mo, 18.03.19 01:04, Tomasz Chmielewski (man...@wpkg.org) wrote:
> How about achieving a similar result with just systemd? Is there some
> system-wide MemoryMax which we could easily set in one place?
The top-leve cgroup doesn't expose functionality for that.
What you probably could do is
On Sa, 16.03.19 05:52, Reindl Harald (h.rei...@thelounge.net) wrote:
> Hi
>
> for a firewall development setup (nested virtualization) i have running
> a tcp service like below on a VM liesting on a complete /24 network
> behind a NAT
>
>
> with "udpsvd" at least something works for "nmap -p 53
Thanks, oomd is an interesting one for more complicated server cases,
especially without any containers involved.
For "my own 1-user desktop" case, I've resorted to
/etc/systemd/system/user-1000.slice on a desktop with 16 GB RAM and
integrated graphics card:
[Slice]
Slice=user.slice
12 matches
Mail list logo
