On Thu, 16 Jan 2025, Luca Boccassi wrote:
>This is an anti-pattern, and best avoided. What's the problem if the
>script runs twice? If it just detects things it should be just fine,
Extra effort, though. And, in general, TOCTOU, but probably not
applicable here.
bye,
//mirabilos
--
den AGP ste
On Thu, 16 Jan 2025, Sven Geuer wrote:
>> If not, I’d lean towards one (which?) of the errorlevel-using ones,
>> because otherwise we’d have to run the detection code twice.
>
>Not sure what you mean by 'one of the errorlevel-using ones'. Please
>explain your idea in more details.
SuccessExitStat
On Wed, 15 Jan 2025, Sven Geuer wrote:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
>Applying ExecCondition to me seems the most reasonable solution to this
>bug.
Can the script behind ExecCondition pass variables to the script
behind ExecStart or, even better, the unit itself
On Tue, 14 Jan 2025, Luca Boccassi wrote:
>It looks like this is doing some checks, and intends to skip. But just
>exiting means the service is recorded as failed, and this will likely
>trip other tests, hence the severity to stop migrating to testing for
>now.
Ah, ouch. Agreed.
>There are sever
On Sat, 26 Oct 2024, Sven Geuer wrote:
>Feel free to integrate my additions into your repo. You might want to
>test the sysv-init functionality still works. According to my tests
>sysv-init and systemd unit work flawlessly at least when running
>autopkgtest from a Qemu VM.
I’ve integrated that, b
On Tue, 13 Jun 2023, Russ Allbery wrote:
>Ah, I think I understand what you're getting at. You're talking about
>using the init script of a daemon as this sort of wrapper script for
Not really. I was talking about normal programs, not dæmons.
I have the expectation that these, when invoked, crea
On Tue, 13 Jun 2023, Russ Allbery wrote:
>namely if you're running anything
>in a chroot that needs directories created in /tmp and /run, the chroot
>either needs to have a persistent /tmp and /run or you have to arrange for
>it to run at least some init scripts during boot.
I very much disagree
On Tue, 13 Jun 2023, Russ Allbery wrote:
>Thorsten Glaser writes:
>
>> Therefore I belive that Policy ought to *not* recommend any solution
>> that depends on starting dæmons or init scripts to create temporary
>> files/directories that are necessary for programs to wor
On Tue, 13 Jun 2023, Bill Allombert wrote:
>I agree, chroots are important to consider, and the system should not
>make assumptions how and why there are used.
Thanks!
>Conversely, sometimes I need to use chroots to test init scripts.
>start-stop-daemon should not refuse to run in a chroot if po
On Mon, 5 Jun 2023, Simon McVittie wrote:
>No init system at all, (C.), can only happen when starting with a
>minbase debootstrap or equivalent (because a default debootstrap
>includes the init metapackage due to its Priority: required). In
>this scenario it *usually* doesn't really matter whether
Michael Biebl dixit:
> Whether it's safe to grant access to /dev/uinput (to local, active users) is
> probably better answered by the kernel maintainers or the maintainer of that
> specific subsystem.
Hm, maybe. But, given my lack of familiarity with udev, does it
indeed give that access to local
Hi,
antimicro’ new upstream version wants to install the following
udev rule file:
#Enable user access to keyboard using uinput event generator
SUBSYSTEM=="misc", KERNEL=="uinput", TAG+="uaccess"
What exactly are the consequences of this? Should I warn users,
or is this safe (current console use
Package: insserv
Version: 1.21.0-1
Severity: wishlist
X-Debbugs-Cc: t...@mirbsd.de, pkg-systemd-maintain...@lists.alioth.debian.org
Cc’ing init-system-helpers maintainer address, as
parts of this probably affect it as well.
From a discussion on debian-init-diversity, using…
sudo /usr/sbi
Hi Neil,
>First, regarding the rng-tools version looks rather out of date. From what
yes. As I explicitly wrote in the first message, this is about the
*heavily* patched “Debian classic” version of rng-tools 2.x; the
package with 5.x is called rng-tools5 currently, and updating it
is tracked els
Hi Felipe,
>I'll comment only on the init stuff, as I have no idea what rng-tools does.
that’s fair. Thanks anyway.
>It is difficult to comment on this without more details. Maybe it would be
>possible to configure socket activation here? If not, the best option is
AIUI socket activation is use
Henrique de Moraes Holschuh dixit:
>On Tue, Nov 10, 2020, at 16:05, Thorsten Glaser wrote:
>> So we additionally have the case where the character device
>> exists but is not usable… oh my.
>
>This was common enough that rngd should know about it and bail out with
>an
Dixi quod…
>among these I (co‑)manage. With “modprobe virtio-rng”, I
>was able to get it on a VM though. Perhaps relevant info:
>
>$ ls -ld /dev/hw*; grep . /sys/devices/virtual/misc/hw_random/*
>crw--- 1 root root 10, 183 Nov 10 17:04 /dev/hwrng
>/sys/devices/virtual/misc/hw_random/dev:10:183
All,
I think due to the complexity of this I’ll postpone
this for after bullseye. Maybe I can get my hands on
systems which Linux /dev/hwrng supports in the mean‐
time, too, and perhaps test both systemd and sysvinit
on those then (help welcome), but for now I’ll leave
this at the refactoring of t
Hi *,
I’m copying this eMail to those who requested various starting
methods for rngd and those who can probably help me with it.
Background: I took over the heavily patched 2.x series of
rng-tools as “rng-tools-debian”, which is currently started
from a sysvinit script only.
Now I have got requ
On Mon, 6 Apr 2020, Thorsten Glaser wrote:
> On Thu, 19 Mar 2020, Thorsten Glaser wrote:
>
> > Nevermind, I found the real culprit. SCMP_SYS() is defined to return int.
>
> I’ll be uploading this to debian-ports’ unreleased repo to get the
> builds going again. Full
retitle 954294 libseccomp-dev: API break: SCMP_SYS() is unsigned long
tags 954294 + patch
thanks
> Nevermind, I found the real culprit. SCMP_SYS() is defined to return int.
Patch attached. Please apply and upload, and forward this upstream.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße
reassign 954294 libseccomp-dev
found 954294 2.4.3-1
affects 954294 src:systemd
thanks
> Here, SCMP_SYS(mmap) is an unsigned long, probably because that’s
> what the native size type is.
Nevermind, I found the real culprit. SCMP_SYS() is defined to return int.
bye,
//mirabilos
--
tarent solution
Source: systemd
Version: 245.2-1
Severity: important
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past),
on non-release architecture
https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=x32&ver=245.2-1&stamp=1584573299&raw=0
The failures se
On Mon, 1 Apr 2019, Felipe Sateler wrote:
> Thanks for linking to the full file. I had not noticed that the unit used a
> specific User. This means a root-owned /var/log/tomcat9 is not going to be
> writable by tomcat. You should probably set it to tomcat9:adm, or add an
Oops, yes, tomcat:adm is
Hi again Felipe,
> If you ship this, there is no need for a LogsDirectory= entry.
But I probably do need to add it with ReadWritePaths if we use
ProtectSystem=strict, correct?
https://salsa.debian.org/java-team/tomcat9/commit/5556481b345049f32720e20d22a072ebd9b865fa
Thanks,
//mirabilos
--
tare
On Fri, 29 Mar 2019, Felipe Sateler wrote:
> It might be a good idea to store that script somewhere else (possibly
> /usr/lib/tomcat9 ?) and call it from the init script. As the script gets
Indeed… the systemd unit calls the scripts from /usr/libexec/tomcat9/
(which is the currently recommended l
Hi Felipe,
> > This won’t delete the logs on shutdown or something, because
> > it’s called tmpfiles?
>
> No, because we don't provide the last argument (the age one):
thanks!
> In fact, /var/log is already tmpfile'd with a similar entry:
OK. I don’t run systemd, so I didn’t know and needed th
Hi Felipe,
> You can ship a tmpfiles snippet like:
>
> d /var/log/tomcat9 2750 root adm -
This won’t delete the logs on shutdown or something, because
it’s called tmpfiles?
> If you ship this, there is no need for a LogsDirectory= entry.
Thanks,
//mirabilos
--
tarent solutions GmbH
Rochusstra
Hi,
how can we make it so that a service that uses LogsDirectory
has its logs readable by group adm?
There is “LogsDirectoryMode=750” which we could change to 2750,
but no way to set the group to adm, and from what I’ve read,
pre-creating the /var/log/tomcat9 (in this case) as 2750 tomcat:adm
wil
prefer syslog over kmsg for auto logging. (Closes: #923559)
+
+ -- Thorsten Glaser Sun, 03 Mar 2019 23:00:57 +0100
+
systemd (241-1) unstable; urgency=medium
[ Adam Borowski ]
diff -Nru
systemd-241/debian/patches/debian/Use-syslog-for-AUTO-logging-before-klog.patch
systemd-241/debian/pa
reopen 923559
thanks
Debian Bug Tracking System dixit:
>If this explanation is unsatisfactory and you have not received a
>better one in a separate message then please contact Michael Biebl
> by
>replying to this email.
This is unsatisfactory.
>>This is expected behaviour. udevd uses the journ
Package: udev
Version: 241-1
Severity: normal
Mar 1 23:09:44 tglase-nb vmunix: [ 125.926361] systemd-udevd[2636]:
link_config: autonegotiation is unset or enabled, the speed and duplex are not
writable.
I expect this instead:
Mar 1 23:09:44 tglase-nb systemd-udevd[2636]: link_config: autone
On Fri, 21 Dec 2018, Dmitry Bogatov wrote:
> I propose to replace current approach with update-alternatives(1)
[…]
> Opinions?
No. update-alternatives is too fragile to handle things like
/bin/sh and init(8).
Also, what Josh Triplett said.
The packages you cited are basically just the hooks to
On Sat, 1 Dec 2018, Michael Biebl wrote:
> If there is a binary implementation, then you would be using
> #!/lib/init/init-d-script
Yes, but it would *also* still work with env(1).
bye,
//mirabilos
--
>> Why don't you use JavaScript? I also don't like enabling JavaScript in
> Because I use lynx
On Sat, 1 Dec 2018, Michael Biebl wrote:
> I'd also be interested to know why
>
> #!/usr/bin/env /lib/init/init-d-script
> is preferred over
> #!/bin/sh /lib/init/init-d-script
> given that init-d-script is *no* C implementation.
That’s easy: this way, the shebang at the start of
/lib/init/init-
On Sat, 1 Dec 2018, Dmitry Bogatov wrote:
> AFAIK, in shell [ "${foo}" ] is equal to [ -n "${foo}" ].
Not always / portably.
I recommend
test -n "$foo"
for POSIX (which is equivalent to [ -n "$foo" ] but better legible and
making it clear that test is an external command, not a langua
Adrian Bunk dixit:
>As an example, what happens if I debootstrap and deploy the resulting
>filesytem to a large number of identical embedded systems without
>entropy sources?
Just get into a habit of not doing so, for example by modifying the
image during each writing process.
Having the bootloa
Theodore Y. Ts'o dixit:
>that problems helps most of our users, and we shouldn't let the
>perfect be the enemy of the good.
Agreed. Start small, then enhance one bootloader at a time.
Or boot protocol, I assume.
>Also note that the bootloader has depend on userspace to refresh the
>seed entropy,
38 matches
Mail list logo
