On Tue, Apr 18, 2023, 02:59 Bill Steinberg wrote:
>
> Hi Barry,
>
> Thanks for the response. Answers inline below.
>
> On Apr 17, 2023, at 5:09 PM, Barry wrote:
>
>
>
> On 17 Apr 2023, at 19:05, Bill Steinberg wrote:
>
> Hello systemd devel,
>
> I have a systemd service that I’ve run on prior
Hi Barry,
Thanks for the response. Answers inline below.
> On Apr 17, 2023, at 5:09 PM, Barry wrote:
>
>
>
>> On 17 Apr 2023, at 19:05, Bill Steinberg wrote:
>>
>> Hello systemd devel,
>>
>> I have a systemd service that I’ve run on prior versions of fedora which
>> fails to start via s
> On 17 Apr 2023, at 19:05, Bill Steinberg wrote:
>
> Hello systemd devel,
>
> I have a systemd service that I’ve run on prior versions of fedora which
> fails to start via systemd on Fedora release 37. It is a oneshot service that
> starts the distributed checksum clearing house’s dccifd s
Hello systemd devel,
I have a systemd service that I’ve run on prior versions of fedora which fails
to start via systemd on Fedora release 37. It is a oneshot service that starts
the distributed checksum clearing house’s dccifd service via a shell script.
Here is the definition of the service:
You wrote:
> Is it actually 3.10 *pretending* to be 5.4 just to make it pass systemd's
> kernel version checks?
Correct. The host machines runs 3.10 and via an OpenVZ configuration
for the container you can overwrite the kernel version in the
container that is reported via "uname -a".
--
Erik
Hi Barry,
I'm not certain how to pinpoint this error. The problem could a
packaging problem or a systemd problem.
I've opened up a ticket at the Canonical launchpad:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2013543.
The last working version was 245.4-4ubuntu3.19.
Any other thought
On Mon, Apr 17, 2023 at 4:48 AM Lennart Poettering
wrote:
>
> On Fr, 14.04.23 09:14, Chuck Tuffli (ctuf...@gmail.com) wrote:
>
> > On Thu, Apr 13, 2023 at 4:14 PM Luca Boccassi
> > wrote:
> > ...
> > > Can't reproduce this either on latest main or on v247. Enable debug
> > > logs with systemctl
On Fr, 14.04.23 09:14, Chuck Tuffli (ctuf...@gmail.com) wrote:
> On Thu, Apr 13, 2023 at 4:14 PM Luca Boccassi wrote:
> ...
> > Can't reproduce this either on latest main or on v247. Enable debug
> > logs with systemctl log-level debug and then restart the service and
> > check again.
>
> Thank y