Am 26.04.2020 um 19:15 schrieb Philip Munts:
I'm trying to send email from OpenBSD 6.6 via GoDaddy's
smtp.secureserver.net. Unfortunately my GoDaddy SMTP username is
"p...@munts.net" which doesn't seem to be a legal username for OpenBSD's
smtpd. I've tried every escaping mechanism for the @
I'm trying to send email from OpenBSD 6.6 via GoDaddy's smtp.secureserver.net.
Unfortunately my GoDaddy SMTP username is "p...@munts.net" which doesn't seem
to be a legal username for OpenBSD's smtpd. I've tried every escaping mechanism for the
@ character I can think of, but nothing has
Hi,
Thanks to your answers, I managed to
record sounds using my webcam, connecting
to rsnd device and, more important, I think
I understood why aucat couldn't find the
device earlier.
I overlooked man sndio (7) because I
misunderstood man sndiod (8) and tried to
connect to /dev/ instead of
Not sure how I missed the clear information in the man page...
"If set to default, a default route pointing to this router will be
announced over OSPF"
It seems I am just having an issue and it should work as I expected.
I will do some more diagnosis in the morning...
On Sun, 26 Apr 2020,
Hi, I have created a OpenBSD 6.6 VM in the Azures cloud that I plan to use as a
Firewall, I had planned on using carp but I can't get it working in Azure so I
think I can use an Internal load balancer to achieve my aim of having two
redundany OBSD Firewalls in Azure. The problem I have is that
Hi,
Hope someone can help, I am having a strange issue and can't seem to
isolate the problem.
We have "redistribute default" set globally on our bgp/ibgp speakers in the
ospfd.conf. The bsd boxes are all 6.6.
These routers are connected via ibgp to some other routers and have
external bgp
On Sun, 26 Apr 2020 13:54:27 +0200, Jan Stary wrote:
> Is there a recommended way to deal with this?
If I correctly understood your problem, the solution:
(from pf.conf(5))
> Host name resolution and interface to address translation are
> done at ruleset load-time. When the address of an
Hi,
Martijn van Duren wrote on Sun, Apr 26, 2020 at 12:52:38PM +0200:
> On 4/26/20 12:27 PM, Thomas de Grivel wrote:
>> Second I don't see this feature described neither in man sh nor man
>> ksh so is it a known behaviour of ksh ?
> from echo(1):
> echo does not support any of the backslash
This is current/amd64 on an APU2.
The machine is connected via pppoe over vlan over em as follows:
$ ifconfig em0
em0: flags=8843 mtu 1500
lladdr 00:0d:b9:56:5e:fc
index 1 priority 0 llprio 3
media: Ethernet autoselect (1000baseT full-duplex)
status: active
$
On Sun, Apr 26, 2020 at 01:04:05PM +0200, Otto Moerbeek wrote:
> On Sun, Apr 26, 2020 at 12:27:24PM +0200, Thomas de Grivel wrote:
>
> > Hello,
> >
> > I was testing some scripting using /bin/sh and I could not find this
> > behaviour in the documentation :
> >
> > > $ /bin/sh
> > > $ echo -n
On Sun, Apr 26, 2020 at 12:27:24PM +0200, Thomas de Grivel wrote:
> Hello,
>
> I was testing some scripting using /bin/sh and I could not find this
> behaviour in the documentation :
>
> > $ /bin/sh
> > $ echo -n '\n'
> >
> > $
>
> It seems that ksh even in sh (posix ?) mode does expansion of
On 4/26/20 12:27 PM, Thomas de Grivel wrote:
> Hello,
>
> I was testing some scripting using /bin/sh and I could not find this
> behaviour in the documentation :
>
>> $ /bin/sh
>> $ echo -n '\n'
>>
>> $
>
> It seems that ksh even in sh (posix ?) mode does expansion of \n to an
> actual
Hello,
I was testing some scripting using /bin/sh and I could not find this
behaviour in the documentation :
> $ /bin/sh
> $ echo -n '\n'
>
> $
It seems that ksh even in sh (posix ?) mode does expansion of \n to an
actual newline.
First is there a way to turn off the \n expansion in simple
13 matches
Mail list logo
