there was a stupid little typo in the pf rules I sent: the ssh port is
obvioulys 22, not 20. That was just a typo in the e-mail, not on the server.
Now here's a mysterious one -- I've been working on this for weeks and still
have no clue what's causing it.
I have couple of virtual servers, running *the* latest 64-bit snapshots.
They're backed up using rsync over ssh. For a long time (months / years)
everything was working
On Fri, 28 Feb 2020 at 18:14, Luke A. Call wrote:
> Another option I found helpful once is to use wget to download the
> FAQs' content to a local copy (unless that puts too much load on the server),
> then have a simple local shell alias to view it with links or w3m.
> (At the time, it was a
Yeah like Stuart said I need to reproduce the crash and get inside the
machine when it’s in that state. To be continued.
On Fri, Feb 28, 2020 at 7:42 PM Avon Robertson wrote:
> On Sat, Feb 29, 2020 at 12:57:07AM +1000, Stuart Longland wrote:
> > On 28/2/20 11:32 pm, Justin Noor wrote:
Awesome - thank you for your time and for the valuable information.
That’s hilarious about the serial port. I’ll try plugging into a switch,
reproducing the crash, and SSHing into it. I still haven’t tried the
syslogd tip you mentioned either. It’s time for me to start learning more
about X. Will
On 2020-02-27, Stuart Longland wrote:
> On 26/2/20 9:46 pm, Marc Espie wrote:
>> (these days, new OS versions will all use the same termcap source, so you're
>> probably safe on anything released over the past 5 years)
People with a need to connect to older OS (from the text console rather
Mail list logo