Gene Heskett composed on 2019-05-26 11:32 (UTC-0400):
...
No network troubles with fixed IP and Trinity on Stretch here:
# /etc/network/interfaces
source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet static
address 192.168.###.###
n
On Wed 29 May 2019 at 06:54:04 -0400, Gene Heskett wrote:
> On Wednesday 29 May 2019 06:48:51 am Reco wrote:
>
> > On Wed, May 29, 2019 at 06:42:34AM -0400, Gene Heskett wrote:
> >
> > > How would I go about disabling n-m with systemctl?
> >
> > "apt-get purge network-manager" allows me not to bo
On Wed, May 29, 2019 at 11:21:47AM -0400, Greg Wooledge wrote:
> On Wed, May 29, 2019 at 04:18:21PM +0100, mick crane wrote:
> > legal people still use fax.
>
> And medical.
>
Which, of course, is utter insanity.
Send medical record by fax* -> A-OK
Send medical record by unencrypted email** ->
On Wed, May 29, 2019 at 04:18:21PM +0100, mick crane wrote:
> legal people still use fax.
And medical.
On 2019-05-29 16:00, Gene Heskett wrote:
On Wednesday 29 May 2019 08:20:02 am Brian wrote:
On Tue 28 May 2019 at 21:47:06 -0400, Gene Heskett wrote:
> On Tuesday 28 May 2019 03:37:55 pm Brian wrote:
> > Why do think cron was calling hpfax? Did you set up the job?
> > (Using fax isn't exactly co
On Wednesday 29 May 2019 08:20:02 am Brian wrote:
> On Tue 28 May 2019 at 21:47:06 -0400, Gene Heskett wrote:
> > On Tuesday 28 May 2019 03:37:55 pm Brian wrote:
> > > Why do think cron was calling hpfax? Did you set up the job?
> > > (Using fax isn't exactly common these day).
yeah, like going b
On Tue 28 May 2019 at 21:47:06 -0400, Gene Heskett wrote:
> On Tuesday 28 May 2019 03:37:55 pm Brian wrote:
>
> > Why do think cron was calling hpfax? Did you set up the job? (Using
> > fax isn't exactly common these day).
> >
> It was cron itself that mentioned it in the syslog.
I'd be inclined
On Wednesday 29 May 2019 06:48:51 am Reco wrote:
> Hi.
>
> On Wed, May 29, 2019 at 06:42:34AM -0400, Gene Heskett wrote:
> > On Wednesday 29 May 2019 12:22:41 am Reco wrote:
> > > On Tue, May 28, 2019 at 04:52:52PM -0400, Gene Heskett wrote:
> > > > On Tuesday 28 May 2019 01:32:31 pm Reco wr
Hi.
On Wed, May 29, 2019 at 06:42:34AM -0400, Gene Heskett wrote:
> On Wednesday 29 May 2019 12:22:41 am Reco wrote:
>
> > On Tue, May 28, 2019 at 04:52:52PM -0400, Gene Heskett wrote:
> > > On Tuesday 28 May 2019 01:32:31 pm Reco wrote:
> > > > On Tue, May 28, 2019 at 01:23:45PM -0400, G
On Wednesday 29 May 2019 12:22:41 am Reco wrote:
> On Tue, May 28, 2019 at 04:52:52PM -0400, Gene Heskett wrote:
> > On Tuesday 28 May 2019 01:32:31 pm Reco wrote:
> > > On Tue, May 28, 2019 at 01:23:45PM -0400, Gene Heskett wrote:
> > > > > End users can remove that '-e' flag if they believe it's
Hi.
On Wed, May 29, 2019 at 06:06:20AM -0400, Gene Heskett wrote:
> > > I'm also seeing several can't connect to d-bus messages, only ID'd
> > > by the pid. That means whatever its pid is, isn't working.
> >
> > Like I wrote earlier - nothing that you put into rc.local belongs
> > there.
On Wednesday 29 May 2019 12:22:41 am Reco wrote:
> On Tue, May 28, 2019 at 04:52:52PM -0400, Gene Heskett wrote:
> > On Tuesday 28 May 2019 01:32:31 pm Reco wrote:
> > > On Tue, May 28, 2019 at 01:23:45PM -0400, Gene Heskett wrote:
> > > > > End users can remove that '-e' flag if they believe it's
On Tue, May 28, 2019 at 04:52:52PM -0400, Gene Heskett wrote:
> On Tuesday 28 May 2019 01:32:31 pm Reco wrote:
>
> > On Tue, May 28, 2019 at 01:23:45PM -0400, Gene Heskett wrote:
> > > > End users can remove that '-e' flag if they believe it's
> > > > problematic. rc.local is a simple shell script
On Tuesday 28 May 2019 03:37:55 pm Brian wrote:
> On Tue 28 May 2019 at 14:20:22 -0400, Gene Heskett wrote:
> > And at that point in composing that reply, the keyboard went dead. I
> > thought that was cron, calling hpfax, and finding it had nothing to
> > do,
>
> Why do think cron was calling hpf
On Tuesday 28 May 2019 01:32:31 pm Reco wrote:
> On Tue, May 28, 2019 at 01:23:45PM -0400, Gene Heskett wrote:
> > > End users can remove that '-e' flag if they believe it's
> > > problematic. rc.local is a simple shell script, open to all kinds
> > > of abuse including this one.
> >
> > I assume
On Tue 28 May 2019 at 14:20:22 -0400, Gene Heskett wrote:
> And at that point in composing that reply, the keyboard went dead. I
> thought that was cron, calling hpfax, and finding it had nothing to do,
Why do think cron was calling hpfax? Did you set up the job? (Using
fax isn't exactly common
On Tuesday 28 May 2019 01:23:45 pm Gene Heskett wrote:
> On Tuesday 28 May 2019 11:53:26 am Reco wrote:
> > Hi.
> >
> > On Tue, May 28, 2019 at 10:53:04AM -0400, Greg Wooledge wrote:
> > > On Mon, May 27, 2019 at 12:11:29PM +0300, Reco wrote:
> > > > On Sun, May 26, 2019 at 05:45:56PM -0400, G
On Tue, May 28, 2019 at 08:42:38PM +0300, Reco wrote:
> On Tue, May 28, 2019 at 01:37:48PM -0400, Greg Wooledge wrote:
> > On Tue, May 28, 2019 at 08:32:31PM +0300, Reco wrote:
> > > Quoting bash(1):
> > >
> > > -e Exit immediately if a pipeline (which may consist of a single
> > > simple comm
Hi.
On Tue, May 28, 2019 at 01:37:48PM -0400, Greg Wooledge wrote:
> On Tue, May 28, 2019 at 08:32:31PM +0300, Reco wrote:
> > Quoting bash(1):
> >
> > -e Exit immediately if a pipeline (which may consist of a single
> > simple command), a list, or a compound command (see SHELL GRAMMA
On Tue, May 28, 2019 at 08:32:31PM +0300, Reco wrote:
> Quoting bash(1):
>
> -e Exit immediately if a pipeline (which may consist of a single
> simple command), a list, or a compound command (see SHELL GRAMMAR
> above), exits with a non-zero status.
No fair snipping out the two paragraphs of
On Tue, May 28, 2019 at 01:23:45PM -0400, Gene Heskett wrote:
> I'll sure as hell 2nd that. If anything, rc.local should stack the errors
> and keep on trucking, and when its out of things to do, then spit out
> the errors if any, in the order encountered, to the syslog.
If you want that behavio
On Tue, May 28, 2019 at 01:23:45PM -0400, Gene Heskett wrote:
> > End users can remove that '-e' flag if they believe it's problematic.
> > rc.local is a simple shell script, open to all kinds of abuse
> > including this one.
> >
> I assume the -e is a bash option?
Any POSIX-compliant shell knows
On Tuesday 28 May 2019 11:53:26 am Reco wrote:
> Hi.
>
> On Tue, May 28, 2019 at 10:53:04AM -0400, Greg Wooledge wrote:
> > On Mon, May 27, 2019 at 12:11:29PM +0300, Reco wrote:
> > > On Sun, May 26, 2019 at 05:45:56PM -0400, Gene Heskett wrote:
> > > > root@coyote:GenesAmandaHelper-0.61$ ca
Hi.
On Tue, May 28, 2019 at 10:53:04AM -0400, Greg Wooledge wrote:
> On Mon, May 27, 2019 at 12:11:29PM +0300, Reco wrote:
> > On Sun, May 26, 2019 at 05:45:56PM -0400, Gene Heskett wrote:
> > > root@coyote:GenesAmandaHelper-0.61$ cat /etc/rc.local
> > > #!/bin/sh -e
> >
> > Any execution
On Mon, May 27, 2019 at 12:11:29PM +0300, Reco wrote:
> On Sun, May 26, 2019 at 05:45:56PM -0400, Gene Heskett wrote:
> > root@coyote:GenesAmandaHelper-0.61$ cat /etc/rc.local
> > #!/bin/sh -e
>
> Any execution error will terminate the script.
The blame is on Debian for that one. That's what Deb
On Monday 27 May 2019 03:31:42 pm Reco wrote:
> On Mon, May 27, 2019 at 02:00:49PM -0400, Gene Heskett wrote:
> > > > May 25 12:03:03 coyote rc.local[884]: read: Connection reset by
> > > > peer
> > >
> > > ...
> > >
> > > > None of which gives me the faintest clue whats wrong with it.
> > >
> > >
On Mon, May 27, 2019 at 02:00:49PM -0400, Gene Heskett wrote:
> > > May 25 12:03:03 coyote rc.local[884]: read: Connection reset by peer
> >
> > ...
> >
> > > None of which gives me the faintest clue whats wrong with it.
> >
> > It does for me.
> >
> > First,
> >
> > > root@coyote:GenesAmandaHelper
On Monday 27 May 2019 05:11:29 am Reco wrote:
> Hi.
>
> On Sun, May 26, 2019 at 05:45:56PM -0400, Gene Heskett wrote:
> > On Sunday 26 May 2019 12:13:38 pm john doe wrote:
> > > On 5/26/2019 5:32 PM, Gene Heskett wrote:
> > > > Greetings all;
> > > >
> > > > New stretch install about 2 weeks
On Monday 27 May 2019 04:50:22 am Curt wrote:
> On 2019-05-26, Gene Heskett wrote:
> > hum:
> > root@coyote:GenesAmandaHelper-0.61$ systemctl status rc.local
> > ● rc-local.service - /etc/rc.local Compatibility
And un-noticed 100 lines later in that same log is a report that the
compati
Hi.
On Sun, May 26, 2019 at 05:45:56PM -0400, Gene Heskett wrote:
> On Sunday 26 May 2019 12:13:38 pm john doe wrote:
>
> > On 5/26/2019 5:32 PM, Gene Heskett wrote:
> > > Greetings all;
> > >
> > > New stretch install about 2 weeks ago, cleaning up the remains.
> > > Fresh disk, so no l
On 2019-05-26, Gene Heskett wrote:
> hum:
> root@coyote:GenesAmandaHelper-0.61$ systemctl status rc.local
> ● rc-local.service - /etc/rc.local Compatibility
>Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor
> preset: enabled)
I found this (not sure if it's entirel
On Sunday 26 May 2019 08:29:27 pm bw wrote:
> In-Reply-To: <201905261132.11943.ghesk...@shentel.net>
>
> >Greetings all;
> >
> >New stretch install about 2 weeks ago, cleaning up the remains.
> > Fresh disk, so no leftovers. But lots of stuff has been copied over
> > from the wheezy disk since
>
On Sunday 26 May 2019 03:34:52 pm Brian wrote:
> On Sun 26 May 2019 at 11:32:11 -0400, Gene Heskett wrote:
> > Greetings all;
> >
> > New stretch install about 2 weeks ago, cleaning up the remains.
> > Fresh disk, so no leftovers. But lots of stuff has been copied over
> > from the wheezy disk si
On Sunday 26 May 2019 12:13:38 pm john doe wrote:
> On 5/26/2019 5:32 PM, Gene Heskett wrote:
> > Greetings all;
> >
> > New stretch install about 2 weeks ago, cleaning up the remains.
> > Fresh disk, so no leftovers. But lots of stuff has been copied over
> > from the wheezy disk since
> >
> > I
On Sun 26 May 2019 at 11:32:11 -0400, Gene Heskett wrote:
> Greetings all;
>
> New stretch install about 2 weeks ago, cleaning up the remains. Fresh
> disk, so no leftovers. But lots of stuff has been copied over from the
> wheezy disk since
All copied stuff is compatible with stretch? You ch
On 5/26/2019 5:32 PM, Gene Heskett wrote:
> Greetings all;
>
> New stretch install about 2 weeks ago, cleaning up the remains. Fresh
> disk, so no leftovers. But lots of stuff has been copied over from the
> wheezy disk since
>
> I have spamassassin enabled in my rc5.d, and I start heyu engine and
Greetings all;
New stretch install about 2 weeks ago, cleaning up the remains. Fresh
disk, so no leftovers. But lots of stuff has been copied over from the
wheezy disk since
I have spamassassin enabled in my rc5.d, and I start heyu engine and heyu
monitor in my rc.local for several years , bu
37 matches
Mail list logo
