Michael Biebl:
> Am 01.03.2017 um 21:51 schrieb Patrick Schleizer:
>> Michael Biebl:
>>> Am 01.03.2017 um 21:35 schrieb Patrick Schleizer:
>>>> Hi!
>>>>
>>>> TLDR:
>>>>
>>>> How should the [Install] section for
Felipe Sateler:
> On Wed, Mar 1, 2017 at 11:39 PM, Patrick Schleizer
> <patrick-mailingli...@whonix.org> wrote:
>> Felipe Sateler:
>>> On Wed, Mar 1, 2017 at 9:50 PM, Patrick Schleizer
>>> <patrick-mailingli...@whonix.org> wrote:
>>>> Felipe
Felipe Sateler:
> On Wed, Mar 1, 2017 at 9:50 PM, Patrick Schleizer
> <patrick-mailingli...@whonix.org> wrote:
>> Felipe Sateler:
>>> On Wed, Mar 1, 2017 at 5:51 PM, Patrick Schleizer
>>> <patrick-mailingli...@whonix.org> wrote:
>>>> Micha
Felipe Sateler:
> On Wed, Mar 1, 2017 at 5:51 PM, Patrick Schleizer
> <patrick-mailingli...@whonix.org> wrote:
>> Michael Biebl:
>>> Am 01.03.2017 um 21:35 schrieb Patrick Schleizer:
>>>> Hi!
>>>>
>>>> TLDR:
>>>>
&
Michael Biebl:
> Am 01.03.2017 um 23:58 schrieb Patrick Schleizer:
>> Michael Biebl:
>>> Am 01.03.2017 um 21:51 schrieb Patrick Schleizer:
>>>> Michael Biebl:
>>>>> Am 01.03.2017 um 21:35 schrieb Patrick Schleizer:
>>>>>> Hi!
>
Michael Biebl:
> Am 01.03.2017 um 21:51 schrieb Patrick Schleizer:
>> Michael Biebl:
>>> Am 01.03.2017 um 21:35 schrieb Patrick Schleizer:
>>>> Hi!
>>>>
>>>> TLDR:
>>>>
>>>> How should the [Install] section for
Michael Biebl:
> Am 01.03.2017 um 21:35 schrieb Patrick Schleizer:
>> Hi!
>>
>> TLDR:
>>
>> How should the [Install] section for static systemd unit file look like?
>
> The obvious question is: why does this service need to be statically
> enabled?
Given
Hi!
TLDR:
How should the [Install] section for static systemd unit file look like?
Long:
Getting a lintian warning if using [Install] section.
I: qubes-whonix: systemd-service-file-missing-install-key
lib/systemd/system/qubes-whonix-redirect-9050.service
N:
N:The systemd service file does
Do you think this warning could / should be removed?
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Package: systemd
Severity: normal
X-Debbugs-CC: whonix-de...@whonix.org
sudo service user@.service status
● user@.service.service - User Manager for UID .service
Loaded: loaded (/lib/systemd/system/user@.service; static; vendor
preset: enabled)
Active: inactive (dead)
Feb 26 17:15:17 user
By Debian stretch default, there are some default systemd user unit
files in `/usr/lib/systemd/user/`.
With a different path on Debian stretch
`/usr/lib/systemd/user/mytest.service`:
```
[Unit]
Description=mytest
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/true
[Install]
Which way is the way to go?
ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
or
ln -s /dev/null /etc/systemd/network/99-default.link
?
(and rebuild the initrd with "update-initramfs -u".)
Is this version dependent, stretch vs buster?
Best regards,
Patrick
Michael Biebl:
> Can you attache the full output of
> systemctl status --user mytest
>
> and the completer mytest.service unit.
You looking into this is appreciated!
cat /etc/systemd/user/mytest.service
[Unit]
Description=mytest
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/true
How to securely load a firewall before networking gets up?
Can you provide a secure, recommended or even canonical example of such
a firewall.service?
It does not become clear from systemd documentation [0] that
DefaultDependencies=no should be used. I also asked about this on the
system mailing
Package: systemd
Severity: wishlist
X-Debbugs-CC: whonix-de...@whonix.org
Dear maintainer,
please document how to use per-user systemd --user services.
- how to do that for a login console
- how to do that for an X session
(If there is any difference.)
Steps I done:
sudo apt-get install
Hi!
TLDR:
How to have an `/etc/xdg/autostart/app.desktop` service wait for a
systemd service?
Long:
I have an app started by `/etc/xdg/autostart/app.desktop` that requires
a systemd service to be started first.
I would like to avoid some sleep/wait/custom code if there is an
existing tool for
Hi!
I would like to have the following debhelper auto generated snippet in
the maintainer script.
# Automatically added by dh_installinit
# In case this system is running systemd, we need to ensure that all
# necessary tmpfiles (if any) are created before starting.
if [ -d /run/systemd/system ]
Package: dh-systemd
Severity: wishlist
Could you please add a feature, so debhelper (dh-systemd) could help
making systemd drop-in overwrite files
(/lib/systemd/system/unit.service.d/override.conf) take effect?
(systemctl daemon-reload + service restart)
(guarded by [ -d /run/systemd/system ])
Hi!
Can debhelper (dh-systemd) help making override files
(/lib/systemd/system/unit.service.d/override.conf) take effect?
(systemctl daemon-reload + service restart)
(Override files shipped by different packages.)
Cheers,
Patrick
___
Package: init-system-helpers
Version: 1.23
Severity: minor
As reported [1] on the debian-systemd mailing list, deb-systemd-helper
will not enable systemd unit files when using spaces.
The spaces in
WantedBy = multi-user.target
are unsupported by `deb-systemd-helper`. It needs to be strictly
Martin Pitt:
Hello Patrick,
Patrick Schleizer [2015-05-20 15:32 +]:
Looks like a bug in `deb-systemd-helper`?
The spaces in
WantedBy = multi-user.target
are unsupported by `deb-systemd-helper`. It needs to be strictly without
spaces.
WantedBy=multi-user.target
Right
related lintian feature request...
warn against usage of spaces, i.e. 'Type = notify' in systemd unit files
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786421
Cheers,
Patrick
___
Pkg-systemd-maintainers mailing list
Looks like a bug in `deb-systemd-helper`?
The spaces in
WantedBy = multi-user.target
are unsupported by `deb-systemd-helper`. It needs to be strictly without
spaces.
WantedBy=multi-user.target
Cheers,
Patrick
___
Pkg-systemd-maintainers mailing
Hi!
Can one somehow distinguish if,
a) the daemon was started during boot or,
b) (re)started by an apt-get install or upgrade?
Can this be distinguished from within the daemon itself?
The use case is here to have script that is run by systemd
'Type=oneshot' only run on boot. Not during
Hi!
Could you have a look at my package please? Created a minimal package
[1] for demonstration of this issue. (Just git clone it and run ./build.)
On a Debian jessie system systemd unit gets installed to
/lib/systemd/system/hellodaemon.service, is functional, but does not get
enabled by default
25 matches
Mail list logo
