Re: realpath(3) on a dangling symlink

2018-06-27 Thread Martijn van Duren
I don't think this change is OK. If we return NULL we should return the appropriate errno related to the readlink miss. There's also another issue here that if we have no trailing slash and the file it points to doesn't exists it still returns the file as if it is correct, even though one componen

Next command of GDB does not work properly unusual

2018-06-27 Thread Masato Asou
Hi tech, I have a problem and I have ad hoc patch to solve this problem. However, this patch is AD HOC. Does anybody have correct solution? The next command of GDB does not work properly. I use OpenBSD 6.3 and /usr/bin/gdb (GDB 6.3). When I debuging my program with next command, I expect stop at

Re: realpath(3) on a dangling symlink

2018-06-27 Thread joshua stein
On Wed, 27 Jun 2018 at 21:35:31 -0500, joshua stein wrote: > symlink("/tmp/link", "/tmp/nonexistent"); Oops, I changed this test code at the last second. The proper test code which incorrectly prints on OpenBSD: resolved realpath of /tmp/nonexistent (returned /tmp/nonexistent), errno is 2

realpath(3) on a dangling symlink

2018-06-27 Thread joshua stein
realpath(3) on a symlink that points to a non-existent path returns that path (but also sets errno), rather than returning NULL and setting errno. This is inconsistent with at least Linux, FreeBSD, and macOS. #include #include #include #include #include #include int main() { cha

next step in synchronizing ber.c and ber.h

2018-06-27 Thread Rob Pierce
The following diff makes ber.c and ber.h identical across ldap, ldapd, and ypldap, and slightly reduces the diff with snmpd. It covers the evolution of a few scattered enhancements, including: - sync proscription of indefinite length BER encoding - sync consistent presence of ber_free_element()

Re: irrsi pkg_info (amd64 - [6.2])

2018-06-27 Thread Stuart Henderson
On 2018/06/27 22:52, Dr. COD wrote: > Hello, > > Could you be so kind to explain me this issue for "irssi" pkg (IRC client > 6.2/[amd64]) > > # pkg_info -f irssi | grep '@depend' | cut -f 3 -d : > > libiconv-1.14p3 > gettext-0.19.8.1p1 > glib2-2.52.3 > libiconv-1.14p3 <-REPEAT > gettext

irrsi pkg_info (amd64 - [6.2])

2018-06-27 Thread Dr. COD
Hello, Could you be so kind to explain me this issue for "irssi" pkg (IRC client 6.2/[amd64]) # pkg_info -f irssi | grep '@depend' | cut -f 3 -d : libiconv-1.14p3 gettext-0.19.8.1p1 glib2-2.52.3 libiconv-1.14p3 <-REPEAT gettext-0.19.8.1p1 <-REPEAT glib2-2.52.3<-RE

Re: pkg_info (vlc)

2018-06-27 Thread Stuart Henderson
On 2018/06/27 22:09, Dr. COD wrote: > Hello all, > > I would like to inform tech team about one problem with our Public > REPOSITORY for 6.2 (amd64): > > *# pkg_info vlc | grep Information | cut -d ':' -f 2* > > I got answer from system: > > *//ftp.openbsd.org/pub/OpenBSD/6.2/packages/amd64

pkg_info (vlc)

2018-06-27 Thread Dr. COD
Hello all, I would like to inform tech team about one problem with our Public REPOSITORY for 6.2 (amd64): *# pkg_info vlc | grep Information | cut -d ':' -f 2* I got answer from system: *//ftp.openbsd.org/pub/OpenBSD/6.2/packages/amd64/vlc-2.2.6p0.tgz* I thing that it's not correct and

Re: more bgpd cleanup

2018-06-27 Thread Sebastian Benoit
reads good running on a machine here without problems ok benno@ Claudio Jeker(cje...@diehard.n-r-g.com) on 2018.06.27 16:55:57 +0200: > My plan is to make struct prefix the main object that holds references to > aspath, nexthop and rib. This diff is the next little step towards that. > > Pass a

more bgpd cleanup

2018-06-27 Thread Claudio Jeker
My plan is to make struct prefix the main object that holds references to aspath, nexthop and rib. This diff is the next little step towards that. Pass a struct prefix to rde_filter and remove some of the arguments which are now fetched from struct prefix. Currently some trickery is needed for exp

Re: sync calloc call in ber.c

2018-06-27 Thread Gleydson Soares
On Wed, Jun 27, 2018 at 10:05:52AM -0400, Rob Pierce wrote: > This ber.c change has been in ldapd since rev 1.1 and was applied to snmpd > back > in 2012. The following diff applies the change to the ldap client and ypldap. > > Ok? looks right, > > Index: usr.bin/ldap/ber.c > =

Re: sync calloc call in ber.c

2018-06-27 Thread Claudio Jeker
On Wed, Jun 27, 2018 at 10:05:52AM -0400, Rob Pierce wrote: > This ber.c change has been in ldapd since rev 1.1 and was applied to snmpd > back > in 2012. The following diff applies the change to the ldap client and ypldap. > > Ok? OK claudio@ > Index: usr.bin/ldap/ber.c >

sync calloc call in ber.c

2018-06-27 Thread Rob Pierce
This ber.c change has been in ldapd since rev 1.1 and was applied to snmpd back in 2012. The following diff applies the change to the ldap client and ypldap. Ok? Index: usr.bin/ldap/ber.c === RCS file: /cvs/src/usr.bin/ldap/ber.c,v r

Re: Unlock sendit-based syscalls

2018-06-27 Thread Visa Hankala
Here is a new version of the f_count atomic update diff. Now all updating of the `f_count' field should use atomic operations, and the `fhdlk' is only used for serializing access to the list of open files. In addition, the role of the `fd_fplock' should be clearer now: its only purpose is to let fd

IP_SENDSRCADDR cmsg_len and dnsmasq

2018-06-27 Thread Vincent Gross
So a while back Alexander Markert sent a bug report regarding sendmsg() behaviour with IP_SENDSRCADDR : https://marc.info/?l=openbsd-tech&m=149276833923905&w=2 This impacts our dnsmasq port : https://marc.info/?l=openbsd-tech&m=149234052220818&w=2 Alexander Markert shows in the first thread the

[PATCH] smsc: set SMSC_MII_BUSY to read/write PHY regs

2018-06-27 Thread Kevin Lo
Hi, The diff below sets SMSC_MII_BUSY bit, which is necessary for PHY to acknowledge a read/write request; from FreeBSD r333096. While here, mask off the PHY address and register. Tested on rpi3. # dmesg |grep smsc smsc0 at uhub1 port 1 configuration 1 interface 0 "Standard Microsystems SMSC95