d library? If SIGPIPE has become more important since the
added support for signed gzip headers (which i guess is related to
this) maby it makes sense to initialize the handler to a known state?
Can you repeat the problem using my python snippet for reference?
--
Patrik Lundin
ubtle-bug/
It talks about how python ignores SIGPIPE and shows how it can be worked
around when using subprocess.Popen.
I can solve the problem by adding the following line in /usr/sbin/pkg_add:
===
$SIG{PIPE} = 'DEFAULT';
===
--
Patrik Lundin
On Sat, Nov 19, 2016 at 03:55:07PM +0100, Patrik Lundin wrote:
> Hello,
>
> I have noticed that pkg_add will behave differently when being executed
> from a script when compared to running it manually on the command line.
>
I forgot to mention that all the testing is done on a
l5/OpenBSD/PackageRepository.pm trying to figure out
what is going on, but so far no luck.
--
Patrik Lundin
On Thu, Nov 03, 2016 at 04:02:50PM -0400, trondd wrote:
>
> You actually have to install OpenBSD into that image. Try -k /bsd.rd first.
>
Ahh, so obvious in retrospect, thank you!
--
Patrik Lundin
B 2.0
Hub" rev 2.00/1.11 addr 7
uhidev1 at uhub5 port 4 configuration 1 interface 0 "Logitech Logitech
Illuminated Keyboard" rev 2.00/55.01 addr 8
uhidev1: iclass 3/1
ukbd0 at uhidev1: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev2 at uhub5 port 4 configuration 1 interface 1 "Logitech Logitech
Illuminated Keyboard" rev 2.00/55.01 addr 8
uhidev2: iclass 3/0, 16 report ids
uhid0 at uhidev2 reportid 3: input=7, output=0, feature=0
uhid1 at uhidev2 reportid 16: input=6, output=6, feature=0
softraid0: incorrect key or passphrase
sd1 at scsibus3 targ 1 lun 0: SCSI2 0/direct fixed
sd1: 205420MB, 512 bytes/sector, 420700170 sectors
===
--
Patrik Lundin
On Thu, Dec 03, 2015 at 05:52:13AM +0800, Tinker wrote:
> On 2015-12-02 08:26, Patrik Lundin wrote:
> >
> >This works well, other than needing this patch since the keydisk is on
> >the same harddrive:
> >http://marc.info/?l=openbsd-misc&m=141450636905550&w=2
&
e
keydisk partition when "destroying" the disk as I did before yet the
installer manages to create the sd1 device as expected.
Thanks for the pointers :).
--
Patrik Lundin
s) software?
>
> Every tips are appreciated.
>
You might want to read divert(4) which describes how to pass packets
from pf to a userland application and back.
--
Patrik Lundin
commands are run, only having an impact after a reboot or power outage,
which the unbounded dd does not achieve (this might not be an achievable
goal at all of course).
--
Patrik Lundin
ps://github.com/ansible/ansible-modules-extras/pull/1296
>
> Let me know if there are other OpenBSD-specific modules you'd like to see
> for ansible.
>
I have added a comment to your pull request regarding the rcctl support
already existing in the main service module.
--
Patrik Lundin
On Wed, Dec 02, 2015 at 01:26:10AM +0100, Patrik Lundin wrote:
>
> I have a custom installer script which automatically creates RAID
> devices and assembles an sd1 CRYPTO device before the ordinary installer
> continues (making the installer use sd1 for the rest of the
> insta
unt=1
===
Yet even when doing this the installer still fails with the "not valid
softraid metadata" error. What am I missing? Where is that metadata
hiding?
--
Patrik Lundin
On Sun, Aug 09, 2015 at 03:52:38PM +0900, joe king wrote:
> linux has blkid .
> in openbsd , what is its substitute ?
>
You can use disklabel(8):
===
# disklabel sd0 | grep duid
===
--
Patrik Lundin
our situation
but otherwise it seems to match what we are working with.
--
Patrik Lundin
On Thu, Jul 02, 2015 at 08:18:52AM +0200, Stefan Sperling wrote:
>
> Your windows box is trying to reach address ff02:2::1:ff51:78e9, a mix of
> 'all routers' ff02::2 and em1's link local address.
> But there is no address in the ff02::/32 prefix on em1 for some reason.
> Note that em0 does have a
On Wed, Jul 01, 2015 at 04:47:25PM +0200, Patrik Lundin wrote:
>
> We will retry using a snapshot and see where we end up.
>
We have now attempted the same setup described earlier, using a current
snapshot.
The first problem of not getting a default route via autoconf when
forwa
ld make it
> easier to work through the rest.
>
Thanks for the pointers, the first commit was pointed at by another
developer off list, and seems like exactly the fix needed for the
initial issue we ran into.
We will retry using a snapshot and see where we end up.
--
Patrik Lundin
how much work it would be to support other prefix
> lengths (e.g. as EUI-64 cannot be uses on non-64-bit prefixes) and
> whether or not it is a worthwhile target to persue.
>
There indeed seems to be some confusion how v6 should behave in the real
world as opposed to (some) papers. This is one of the reasons I wanted
to lift the issues with the mailing list.
--
Patrik Lundin
is enabled.
===
So basically, setting it to 0 disables the handling of router advertisements,
setting it to 1 accepts them given that forwarding is disabled (pretty close
to what we are seeing OpenBSD doing right now when handling of RAs are enabled)
and 2 makes it handle the RAs without any regard of forwarding status (what we
would probably need in this SOHO case).
--
Patrik Lundin
the prefix should be
routed to you.
--
Patrik Lundin
- Original message -
From: Giancarlo Razzolini
To: "Openbsd-Misc"
Subject: IPV6 routing issue
Date: Thu, 25 Jun 2015 21:06:51 -0300
HI all,
I've recently changed my ISP and they have native IPv6. My cus
>
Here we can see that you have successfully queried NSD for
blahms01.domain.com. We can also see, as was shown with nslookup, the
warning about recursion: "recursion requested but not available".
This is normal, since NSD will only serve zones it is authoritative for.
This also means you would not query NSD for "openbsd.org" for
example, since NSD will not handle such an recursive query for you. For
this you need unbound.
--
Patrik Lundin
arch for short names is not the job of a DNS server,
it is the job of your stub resolver library.
--
Patrik Lundin
lan, using "nslookup blahname" returns:
> >>
> >>"Server: blahname2.domain.com
> >>Address: 10.0.2.1
> >>
> >>*** blahname2.domain.com can't find blahname: Query refused"
> >>
The main reason I would expect a "REFUSED" response from NSD would be if
you queried it for a domain name that it was not authoritative for.
Again, please show the results of dig(1) (including the commandline
used).
--
Patrik Lundin
hat variable be
set.
--
Patrik Lundin
escribed was an old macppc Mac mini:
# ls -l /var/db/ntpd.drift
-rw-r--r-- 1 root wheel 13 Jan 12 07:25 /var/db/ntpd.drift
# cat /var/db/ntpd.drift
2.405187e-03
I'll post a dmesg below in case it is interesting.
Regards,
Patrik Lundin
OpenBSD 5.6-stable (GENERIC) #0: Sun Dec 14 12:50:41
the contents of the result field ("OK. All NS records are the
same at the parent and at your nameservers.") It appears to me this test
compares your authoritative NS records with the delegation NS records
in the parent. It does not look like it has anything to do with glue
records.
Sorry if
S in the future
:).
Thanks again!
Regards,
Patrik Lundin
makes the bootloader stop at the passphrase prompt.
Thanks a lot!
Regards,
Patrik Lundin
On Mon, Oct 27, 2014 at 07:14:10PM +0100, Patrik Lundin wrote:
>
> Given that wd0d is used for the keydisk, do you mean i
> should use wd0e for the remainder of the drive instead of 'a'?
>
> Would this also mean I should skip creating a sd0a altogether?
>
Of cou
Thank you Stefan for taking a look, see comments inline:
On Mon, Oct 27, 2014 at 12:32:30PM +0100, Stefan Sperling wrote:
> On Sun, Oct 26, 2014 at 09:19:25PM +0100, Patrik Lundin wrote:
> >
> > # disklabel -E wd0
> > Create the following partitions (in this orde
where wd0a with the
passphrase was originally. As if there are some remains that makes it
possible for the bootloader to locate it or something (that is not
overwritten when it is used as the target for the -k argument.
Any input on this would be greatly appreaciated!
Regards,
Patrik Lundin
tl first appeared in OpenBSD 5.7.
>
By "recent" i mean a version that supports the 'default' argument:
http://marc.info/?l=openbsd-cvs&m=141303663711396&w=2
I am very happy that armani@ started the ansible work as early as
he did so we were were able to request features before rcctl was
officially released!
Regards,
Patrik Lundin
On Sat, Sep 13, 2014 at 02:39:04AM +0200, Patrik Lundin wrote:
>
> armani@ has laid the groundwork for this and I recently started
> contributing to his fork as well.
>
> The work-in-progress can be found here:
> https://github.com/jarmani/ansible/tree/openbsd_rcctl/library
d I recently started
contributing to his fork as well.
The work-in-progress can be found here:
https://github.com/jarmani/ansible/tree/openbsd_rcctl/library/system
Regards,
Patrik Lundin
ipermail/unbound-users/2014-September/003504.html
Regards,
Patrik Lundin
his running for a while the issue could "walk around" as the
cache expired etc.
But I am still unsure if this is actually a bug or if it is just
"undefined behaviour from doing silly things with stub-zones". The silly
thing being telling unbound the server was authorative for a zone that
was actually outside the zone apex of the authorative data.
Regards,
Patrik Lundin
t;
I was not aware this was the case, but testing proves you right. Thanks
for setting me straight :).
Regards,
Patrik Lundin
orks
# dig @127.0.0.1 -x 10.0.0.2 <-- fails
# dig @127.0.0.1 -x 10.0.0.3 <-- works
# dig @127.0.0.1 -x 10.0.0.4 <-- works
Basically the first lookup works, the second ends up at IANA (as if the
stub-zone configuration did not exist), and any
following lookups work again.
It might be considered bad to tell unbound a server is authorative for a
wider zone than it actually is though, can this be the same problem you
saw?
Regards,
Patrik Lundin
nitial message I was under the impression the SERVFAIL occurs
after every reboot. Seems it is more complex then :).
Regards,
Patrik Lundin
gt; Is maybe my box (soekris net5501) too slow, so that NSD doesn't answer fast
> enough? Then, after some restarts of unbound, and queries to NSD, then
> NSD has all in memory and then it just works? But then I don't understand
> why it works without flaws for the forward zone, and also the IPv6 zone?
>
Seems far fetched to me.
Regards,
Patrik Lundin
output of
dig(1), any changes made to the unbound configuration etc?
I guess recording what unbound is doing during a bad lookup with
ktrace(1) and sharing the resulting log could be helpful as well if
there is nothing interesting in the system logs.
Regards,
Patrik Lundin
the unprivileged _unbound
> user. Privilege separation would be desirable for this.
>
Just out of curiosity: how come the shipped unbound.conf file mentions
the "module-config:" setting? It appears to me that "validator iterator"
is the default, or am i missing something?
Regards,
Patrik Lundin
is it possible you are running into some state
limit?
On a system that is currently showing the nsd error messages, what does
"pfctl -si" show? I would specifically look at the "memory" counter. If
that counter is something other than 0 you are running into the current
state limit (shown with "pfctl -sm").
Regards,
Patrik Lundin
On Fri, Dec 06, 2013 at 08:35:52PM +0100, Patrik Lundin wrote:
>
> Given the +trace output you supplied that address is not part of the
> trail from the DNS root, and in that case the only involvement is
> answering the initial equivalent of "dig @216.146.35.35 . NS".
>
lied that address is not part of the
trail from the DNS root, and in that case the only involvement is
answering the initial equivalent of "dig @216.146.35.35 . NS".
Regards,
Patrik Lundin
appening on the wire?
Regards,
Patrik Lundin
On Fri, May 31, 2013 at 06:45:18AM +0200, Patrik Lundin wrote:
>
> I am currently testing this patch, I will report back once I have
> some results.
>
So have have tried to stress test the patch, and while it seems to
superficially work it doesnt really seem stable.
I have writ
On Tue, May 28, 2013 at 04:51:34PM -0400, Ted Unangst wrote:
>
> Indeed, I think maybe this is ok.
>
> Index: ffs_vfsops.c
> ===
> RCS file: /cvs/src/sys/ufs/ffs/ffs_vfsops.c,v
> retrieving revision 1.136
> diff -u -p -r1.136 ffs_vfs
On Tue, May 28, 2013 at 01:54:50PM -0400, Ted Unangst wrote:
>
> The softdep flag is cleared when you change a mount to read only. What
> would a read only softdep filesystem do?
>
I was only surprised that updating a filesystem to read-only and back to
read/write would result in another state th
bsd-misc&m=132511441117536&w=2
Since rsync with --link-dest is pretty much creating a hardlink tree,
maby I shouldn't be using softdeps at all for this?
Regards,
Patrik Lundin
fc4861' sysctl
flag mentioned at
http://www.freebsd.org/security/advisories/FreeBSD-SA-08:10.nd6.asc
could be used for the odd cases where it's needed?
Regards,
Patrik Lundin
message can be read here:
http://old.nabble.com/Problems-building-1.5.2-on-OpenBSD-5.1-current-td33566242.html
Regards,
Patrik Lundin
work when the process I wanted to get a core
dump from was
already misbehaving.
I am a bit out of my league here but my question is simply if the lack of gcore
is due to someone considering it to be fundamentally flawed or anything, or if
it is just that no one has considered it important/interesting enough
to hack on.
If there is a better way to do this this then any pointers are appreciated.
Regards,
Patrik Lundin
54 matches
Mail list logo
