Hi there I've got a strange process that spawn from init in the environment
above. No network traffic. Look ahead:
|-+= 51452 root login -p -- \^[[7~\^[[7~\^[[7~\^[[7~\^[[7~\^[[7~\^[[7~\^[[7
| \--- 73422 root passwd -v login=yes -s login --
\^[[7~\^[[7~\^[[7~\^[[7~\^[[7~\^[[7~\^[[7~\^[[7 default
On 2/15/21 2:14 PM, Ed Ahlsen-Girard wrote:
> I am confident that I can speak for for ... a non-zero number of
> people who use sysupgrade the way it says to on the box and would miss
> it if it went away.
+1
Even though it is a little surprising that some people don't realise how easy it
is
On Mon, February 15, 2021 11:14 am, Ed Ahlsen-Girard wrote:
> I am confident that I can speak for for ... a non-zero number of
> people who use sysupgrade the way it says to on the box and would miss
> it if it went away.
>
+1 . Its simple to use, stable, convenient, luckly will bring more p
ANSI sequences appeared on ttyC0.
init is running getty there, which exec'd login, which is running
login_passwd to perform a login.
Riccardo Giuntoli wrote:
> Hi there I've got a strange process that spawn from init in the environment
> above. No network traffic. Look ahead:
>
> |-+= 51452
On Tue, February 16, 2021 1:16 pm, Mitch K. wrote:
>
> I've been unaware of sysupgrade until now. Looks like it was introduced
> in 6.6.
>
> I've done several dot release upgrades manually. The process is
> straightforward and
> well-documented, like the rest of OpenBSD. It took me ~15-30 minutes p
I'm going to assume your acme-client configuration is in order and that
you are using httpd as your web server.
Did you not perhaps forget to reload httpd via rcctl after renewing your
certificate? Otherwise, I suspect you're going to have to give us more
context.
Regards,
Jean-Pierre
On 21/02/
On Tue, February 16, 2021 1:47 pm, Teno Deuter wrote:
> OpenBSD 6.9-beta (GENERIC) #328: Mon Feb 15 10:31:18 MST 2021
>
> I run:
>
> # acme-client -vF <>.com
> acme-client: /etc/ssl/<>.com.crt: certificate valid: 89 days
> left
> acme-client: /etc/ssl/<>.com.crt: forcing renewal
> acme-client: http
On Tue, Feb 16, 2021 at 08:47:52AM -0700, Theo de Raadt wrote:
> ANSI sequences appeared on ttyC0.
Someone tapped a "Home" key? "ESC [ 7 ~" is the "Home" VT sequence.
>
> init is running getty there, which exec'd login, which is running
> login_passwd to perform a login.
>
>
>
> Riccardo G
Kevin Chadwick wrote on Tue [2021-Feb-16 12:52:42 +]:
> On 2/15/21 2:14 PM, Ed Ahlsen-Girard wrote:
> > I am confident that I can speak for for ... a non-zero number of
> > people who use sysupgrade the way it says to on the box and would miss
> > it if it went away.
>
> +1
>
> Even t
OpenBSD 6.9-beta (GENERIC) #328: Mon Feb 15 10:31:18 MST 2021
I run:
# acme-client -vF <>.com
acme-client: /etc/ssl/<>.com.crt: certificate valid: 89 days left
acme-client: /etc/ssl/<>.com.crt: forcing renewal
acme-client: https://acme-v02.api.letsencrypt.org/directory: directories
acme-client: a
after "rcctl reload httpd" everything works well. Thank you very much.
I'm running this configuration since early 6.8 and I don't think that I was
restarting the server! That's why I got now surprised.
On Tue, Feb 16, 2021 at 7:32 PM Jean-Pierre de Villiers <
jeanpie...@jeanpierredevilliers.xyz>
Thank you very much for this in-depth explanation. Appreciate your kind and
valuable reply.
I just noticed that restarting the httpd server is included in the examples
section of the acme-client man page too!
https://man.openbsd.org/acme-client.1
Unfortunately didn't pay the necessary attention
Stuart,
Thank you so much for this. I was able to get things working with your
configuration guidance.
Seth
On 2021-02-13 05:18, Stuart Henderson wrote:
> On 2021-01-21, Seth Hanford wrote:
>> I'm trying unsuccessfully to create a central syslogd logging server
>> between two OpenBSD 6.8 ho
howdee,
wellp - it took 36-ish hours, but after swapping my /xtra and /usr/obj
partitions
the following seems to be the "answer" for my single-data point...
fw$ df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/sd0a 986M121M816M13%/
/dev/sd0k 18.8G1.5
Hi Stefan,
Stefan Sperling wrote:
Sounds like a wrong key, or the wrong type of crypto.
Are you the AP is using WEP? Perhaps you need 'wpakey' instead of 'nwkey'?
If the key is wrong or the crypto is wrong, would the interface still be
active and connected?
I am sure the AP is using WEP: I
15 matches
Mail list logo
