Tue, 29 Apr 2025 13:48:17 -0400
Charles Dennett kirjoitti:
> On 4/29/25 12:54 PM, jarmo wrote:
>
> > But... As said, it was running ok, so far, when
> > came new kernel, updated, rebooted computer, postfix
> > sevice didn't start. In F41 it worked ok, when after kernel
> > update rebooted..
> >
On Tue, Apr 29, 2025 at 4:53 AM Samuel Sieb wrote:
> On 4/29/25 1:10 AM, Javier Perez wrote:
> > Help. Looking at the about systemd-resolved question prompted me to try
> > to clear a problem I am having with local DNS.
> > My home system have few pcs and other devices, some of them with static
>
>
>
On Tue, Apr 29, 2025 at 4:12 AM Barry wrote:
>
>
> On 29 Apr 2025, at 09:11, Javier Perez wrote:
>
>
> Help. Looking at the about systemd-resolved question prompted me to try to
> clear a problem I am having with local DNS.
> My home system have few pcs and other devices, some of them w
On 4/29/25 12:54 PM, jarmo wrote:
But... As said, it was running ok, so far, when
came new kernel, updated, rebooted computer, postfix
sevice didn't start. In F41 it worked ok, when after kernel
update rebooted..
This F42 have something, what makes postix sevice disabled
after reboot, again af
> Am 29.04.2025 um 13:50 schrieb jarmo :
>
> Tue, 29 Apr 2025 12:39:53 +0200
> Peter Boy Uni kirjoitti:
>
>
>> That’s a regression since F41.
>>
>> When you issue an systemctl status postfix just after reboot, you
>> should get a short information about the reason. I suppose it is a
>> com
Tue, 29 Apr 2025 09:13:48 -0700
Mike Wright kirjoitti:
>
> Read what I posted to you before. It is disabled. That means it
> will NOT START automatically. You must enable it in order for it to
> be started automatically.
>
> the command "systemctl enable --now postfix" will set it to be
> sta
On Tue, 2025-04-29 at 22:36 +0930, Tim via users wrote:
> On Tue, 2025-04-29 at 11:07 +0100, Patrick O'Callaghan wrote:
> > You seem to be blaming the list for the user's alleged mistakes. I
> > don't see the logic.
>
> I do suppose that more than one of us should have noticed it and told
> the or
On 4/29/25 08:35, jarmo wrote:
Tue, 29 Apr 2025 07:10:46 -0700
Mike Wright kirjoitti:
On 4/29/25 04:50, jarmo wrote:
Loaded: loaded (/usr/lib/systemd/system/postfix.service; disabled;
preset: disabled)
That line says it is disabled.
Try "systemctl enable --now postfix", then "systemctl st
Tue, 29 Apr 2025 07:10:46 -0700
Mike Wright kirjoitti:
> On 4/29/25 04:50, jarmo wrote:
> > Loaded: loaded (/usr/lib/systemd/system/postfix.service; disabled;
> > preset: disabled)
>
> That line says it is disabled.
>
>
> Try "systemctl enable --now postfix", then "systemctl status
> postfix
On Tue, 2025-04-29 at 14:50 +0300, jarmo wrote:
> systemctl status postfix
> ○ postfix.service - Postfix Mail Transport Agent
> Loaded: loaded (/usr/lib/systemd/system/postfix.service; disabled;
> preset: disabled)
> Drop-In: /usr/lib/systemd/system/service.d
> └─10-timeout-a
On Tue, Apr 29, 2025, at 6:06 AM, Tim via users wrote:
> On Tue, 2025-04-29 at 11:07 +0100, Patrick O'Callaghan wrote:
>> You seem to be blaming the list for the user's alleged mistakes. I
>> don't see the logic.
>
> I do suppose that more than one of us should have noticed it and told
> the origin
Tim:
> > Bearing in mind that even *then* there have been cases of the network
> > not actually being up and running before being declared it was. I'm
> > beginning to think we need either a post-boot target, or at least an
> > improvement on the network is up decision making.
Benny Lyne Amorsen:
On Tue, 2025-04-29 at 16:12 +0200, Benny Lyne Amorsen wrote:
> The recommended solution is to trigger service start off incoming
> connections, if possible. This is less ideal for things like Postfix
> which might need to send traffic before they receive it.
On this computer we don't break the law
On Tue, Apr 29, 2025 at 8:20 AM George N. White III
wrote:
> On Mon, Apr 28, 2025 at 2:03 PM Patrick Dupre via users <
> users@lists.fedoraproject.org> wrote:
>
>> Hello,
>>
>> If I am correct, there was a sagemath package in the past, but it seems
>> that it is not available anymore.
>> Could so
Tim via users writes:
> Bearing in mind that even *then* there have been cases of the network
> not actually being up and running before being declared it was. I'm
> beginning to think we need either a post-boot target, or at least an
> improvement on the network is up decision making.
network-
On 4/29/25 04:50, jarmo wrote:
Loaded: loaded (/usr/lib/systemd/system/postfix.service; disabled; preset:
disabled)
That line says it is disabled.
Try "systemctl enable --now postfix", then "systemctl status postfix".
See if that status changes.
--
_
Hi
On Tue, 29 Apr 2025 22:06:28 +0930 Tim via users wrote:
> Barry kirjoitti:
>> > Being enabled is not necessarily enough.
>> > It must be enabled for the default target.
>> >
>> > Is it wanted by the default target?
/usr/lib/systemd/system/postfix.service states to enable it in
the multi-use
On Tue, 2025-04-29 at 11:07 +0100, Patrick O'Callaghan wrote:
> You seem to be blaming the list for the user's alleged mistakes. I
> don't see the logic.
I do suppose that more than one of us should have noticed it and told
the original poster about it.
I skimmed over it and didn't really notice
Barry kirjoitti:
> > Being enabled is not necessarily enough.
> > It must be enabled for the default target.
> >
> > Is it wanted by the default target?
> >
jarmo:
> Is this what you mean?
> systemctl enable postfix
> Created symlink
> '/etc/systemd/system/multi-user.target.wants/postfix.servi
On Tue, 2025-04-29 at 03:10 -0500, Javier Perez wrote:
> Help. Looking at the about systemd-resolved question prompted me to
> try to clear a problem I am having with local DNS.
> My home system have few pcs and other devices, some of them with
> static ip addresses set at my local router.
> My si
See this message in the thread "Merge /usr/bin & /usr/sbin after upgrade
to F42?" maybe ?
Hope, this helps a bit.
Theo.
Forwarded Message
Subject:Re: Merge /usr/bin & /usr/sbin after upgrade to F42?
Date: Mon, 28 Apr 2025 18:03:26 +0200
From: francis.montag
Tue, 29 Apr 2025 12:39:53 +0200
Peter Boy Uni kirjoitti:
> That’s a regression since F41.
>
> When you issue an systemctl status postfix just after reboot, you
> should get a short information about the reason. I suppose it is a
> complain about network availability at the point of time syste
On Mon, Apr 28, 2025 at 2:03 PM Patrick Dupre via users <
users@lists.fedoraproject.org> wrote:
> Hello,
>
> If I am correct, there was a sagemath package in the past, but it seems
> that it is not available anymore.
> Could somebody clarifies the situation?
>
> Linux is suffering from limited dev
> Am 29.04.2025 um 10:51 schrieb jarmo :
>
> Where to look, postfix service won't start
> after reboot? Have to start manually every
> time...
> And yes service is enabled. Happens every
> time, when update kernel...?
That’s a regression since F41.
When you issue an systemctl status postfix
On Mon, 2025-04-28 at 20:26 -0400, Jonathan Billings wrote:
> You’ve posted both your user’s and root’s hashed passwords to a public list,
> AND mentioned that you’ve got ssh open to the world. I imagine your email
> headers probably also have your IP.
> Well…
>
> Good luck. I can’t take it any
On 4/29/25 1:10 AM, Javier Perez wrote:
Help. Looking at the about systemd-resolved question prompted me to try
to clear a problem I am having with local DNS.
My home system have few pcs and other devices, some of them with static
ip addresses set at my local router.
My situation is that name
Tue, 29 Apr 2025 10:09:21 +0100
Barry kirjoitti:
> Being enabled is not necessarily enough.
> It must be enabled for the default target.
>
> Is it wanted by the default target?
>
> Barry
Is this what you mean?
systemctl enable postfix
Created symlink
'/etc/systemd/system/multi-user.target.want
On 29 Apr 2025, at 09:11, Javier Perez wrote:Help. Looking at the about systemd-resolved question prompted me to try to clear a problem I am having with local DNS.My home system have few pcs and other devices, some of them with static ip addresses set at my local router.My situation is that name
> On 29 Apr 2025, at 09:52, jarmo wrote:
>
> Where to look, postfix service won't start
> after reboot? Have to start manually every
> time...
> And yes service is enabled. Happens every
> time, when update kernel...?
Being enabled is not necessarily enough.
It must be enabled for the default
Where to look, postfix service won't start
after reboot? Have to start manually every
time...
And yes service is enabled. Happens every
time, when update kernel...?
Jarmo
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an
Help. Looking at the about systemd-resolved question prompted me to try to
clear a problem I am having with local DNS.
My home system have few pcs and other devices, some of them with static ip
addresses set at my local router.
My situation is that name resolution does not always work.
For example
> On 4/28/25 5:23 PM, Patrick Dupre via users wrote:
> > ○ sleep.target
> > Loaded: masked (Reason: Unit sleep.target is masked.)
> > Active: inactive (dead)
> >
> > ○ suspend.target
> > Loaded: masked (Reason: Unit suspend.target is masked.)
> > Active: inactive (dead)
>
32 matches
Mail list logo
