On 20/3/22 6:41 am, Jeremy Ardley wrote:
Does anybody have a working example of postfix with postscreen and
spamassassin all working together?
I have now found that 'pass' stanzas for each SMTP IP on a multi-homed machine
are ignored. The only pass stanza that is used is the generic SMTP
Does anybody have a working example of postfix with postscreen and
spamassassin all working together?
* In the first instance on a single homed machine.
* Then on a multi-homed machine so stanzas are individual to each IP
address.
* And finally a version that also works with haproxy.
On Sat, 19 Mar 2022 07:31:04 -0700
Peter Ehlert wrote:
> I now have both needrestart and needrestart-session installed.
>
> Question: do either run in the background?
Apt calls needrestart, so it isn't necessary to run it in the
background.
Unattended upgrades will inform you of which
On 3/19/22, Peter Ehlert wrote:
>
> On 3/19/22 06:32, piorunz wrote:
>> On 19/03/2022 10:02, songbird wrote:
>>
>>>there is also package debian-goodies which has the
>>> command checkrestart. i'm not sure which is better.
>>>
>>
>> All I know is that needrestart works for me, it correctly
Ottavio Caruso wrote:
> Why is it always a pain to mount my Android phone on my Laptop?
Do you have mtp-tools installed? I found that mounting my phone got a
lot more reliable after I installed that package.
best regards,
mike
On 3/19/22, piorunz wrote:
> On 19/03/2022 02:32, Lee wrote:
>> How to tell if I need to reboot the machine after updating the software?
>
> install "needrestart" package.
>
> Description: needrestart checks which daemons need to be restarted after
> library upgrades.
> It is inspired by
This bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895378
sky2: sky2: did not recover correctly after waking up from S3
seems to be fixed on Ubuntu here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921
Will this fix get to Debian? I guess it will go up to kernel
On Sat 19 Mar 2022 at 10:15:45 -0500, David Wright wrote:
> On Fri 18 Mar 2022 at 20:57:38 (+), Brian wrote:
> > On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
> >
> > [...]
> >
> > > Install iwd, and resolvconf if necessary. You may then need to reboot
> > > if the wifi
On Sat, 19 Mar 2022 10:15:27 -0400
Cindy Sue Causey wrote:
Hello Cindy,
>admin emails sent to them as a potential remedy. It's on my to-do to
>play around with those emails to see if that catches those upgrade
>messages..
What they include is advisory notices that get thrown up (when using
On Fri 18 Mar 2022 at 20:57:38 (+), Brian wrote:
> On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
>
> [...]
>
> > Install iwd, and resolvconf if necessary. You may then need to reboot
> > if the wifi interface has already been renamed by the kernel, ie if
> > it's not wlan0. (With
On Fri 18 Mar 2022 at 14:08:36 (-0500), Nicholas Geovanis wrote:
> On Thu, Mar 17, 2022, 11:57 PM David Wright wrote:
> > On Thu 17 Mar 2022 at 12:12:28 (+), Thomas Pircher wrote
> > >
> > > Cool. If you just type resolvectl, it will show you which information it
> > > got on each interface.
>
On Sat, Mar 19, 2022 at 7:33 AM Brian wrote:
> On Fri 18 Mar 2022 at 20:57:38 +, Brian wrote:
>
> > On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
> >
> > [...]
> >
> > > Install iwd, and resolvconf if necessary. You may then need to reboot
> > > if the wifi interface has already
On Sat, Mar 19, 2022 at 10:04:59AM -0500, Nicholas Geovanis wrote:
> On Fri, Mar 18, 2022 at 9:35 PM Greg Wooledge wrote:
>
> > On Fri, Mar 18, 2022 at 10:32:49PM -0400, Lee wrote:
> > > How to tell if I need to reboot the machine after updating the software?
> >
> > Reboots are needed if you
On Fri, Mar 18, 2022 at 9:35 PM Greg Wooledge wrote:
> On Fri, Mar 18, 2022 at 10:32:49PM -0400, Lee wrote:
> > How to tell if I need to reboot the machine after updating the software?
>
> Reboots are needed if you got a new kernel, or new firmware, or new
> microcode, or a new version of the
On 3/19/22 06:32, piorunz wrote:
On 19/03/2022 10:02, songbird wrote:
there is also package debian-goodies which has the
command checkrestart. i'm not sure which is better.
songbird
All I know is that needrestart works for me, it correctly prompts for
computer reboot after kernel
On 3/19/22, Greg Wooledge wrote:
> On Sat, Mar 19, 2022 at 10:55:03AM +0100, Toni Mas Soler wrote:
>> I restart Dbus from time to time. Actually, I stop Dbus if i don't
>> need, that is when I do not use X (almost allways).
>> Do you mean my action is not effective?
>
> The fact that you're
On 19/03/2022 10:02, songbird wrote:
there is also package debian-goodies which has the
command checkrestart. i'm not sure which is better.
songbird
All I know is that needrestart works for me, it correctly prompts for
computer reboot after kernel upgrade; and offers to restart
On Sat, Mar 19, 2022 at 10:55:03AM +0100, Toni Mas Soler wrote:
> I restart Dbus from time to time. Actually, I stop Dbus if i don't
> need, that is when I do not use X (almost allways).
> Do you mean my action is not effective?
The fact that you're "almost always" not using X is probably
piorunz wrote:
> On 19/03/2022 02:32, Lee wrote:
>> How to tell if I need to reboot the machine after updating the software?
>
> install "needrestart" package.
>
> Description: needrestart checks which daemons need to be restarted after
> library upgrades.
> It is inspired by checkrestart from
On Fri 18 Mar 2022 at 20:57:38 +, Brian wrote:
> On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
>
> [...]
>
> > Install iwd, and resolvconf if necessary. You may then need to reboot
> > if the wifi interface has already been renamed by the kernel, ie if
> > it's not wlan0. (With
On 19/03/2022 09:06, Stella Ashburne wrote:
No thank you. I won't touch NetworkManager or its variants with a ten foot
pole. Why?
Reason #1
[quote] I am sorry but we do not support NetworkManager.
I would go so far as to say do not use it at all .. but Linux distros think it
is some sort of
On 2022-03-19 13:19, Eduardo M KALINOWSKI wrote:
On 19/03/2022 09:06, Stella Ashburne wrote:
No thank you. I won't touch NetworkManager or its variants with a ten
foot pole. Why?
Reason #1
[quote] I am sorry but we do not support NetworkManager.
I would go so far as to say do not use it at
Mon cheri
Thanks for your reply.
> Sent: Saturday, March 19, 2022 at 3:17 PM
> From: "Tim Woodall"
> To: "Stella Ashburne"
> Cc: "debian-user mailing list"
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
Mon cheri
> Sent: Saturday, March 19, 2022 at 7:13 PM
> From: "Eduardo M KALINOWSKI"
> To: debian-user@lists.debian.org
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
>
> That's exactly the kind of situation
Hi,
19 mars 2022, 12:16 de edua...@kalinowski.com.br:
> The needrestart package will offer to restart services affected when there'a
> a library update, and it also warns you when the kernel has been udpated (and
> a reboot is necessary). It just doesn't warn you about microcode updates,
>
On 18/03/2022 23:47, Lee wrote:
So
it would be nice if there was some program that would just say that I
needed to reboot
The needrestart package will offer to restart services affected when
there'a a library update, and it also warns you when the kernel has been
udpated (and a reboot is
On 18/03/2022 23:14, Stella Ashburne wrote:
Hi
There are instances in which my machine is connected to a mobile hotspot. And
in some situations, it's connected to a smartphone via USB tethering. And when
I'm in the office, I may connect it to a LAN cable.
Below are the contents of my
I restart Dbus from time to time. Actually, I stop Dbus if i don't
need, that is when I do not use X (almost allways).
Do you mean my action is not effective?
Toni Mas
Missatge de piorunz del dia ds., 19 de març 2022 a les 5:55:
>
> On 19/03/2022 02:32, Lee wrote:
> > How to tell if I need to
ifdown usb0
edit file
ifup wlo1
Will avoid the need to reboot.
You can use mapping lines to achieve the same thing.
mapping eth0
script /usr/local/sbin/map-scheme
iface eth0_home inet static
address 192.168.1.3
netmask 255.255.255.0
gateway 192.168.1.254
29 matches
Mail list logo
