On 7/15/19 12:45 PM, Claudio Jeker wrote:
On Mon, Jul 15, 2019 at 11:08:53AM +0300, Vadim Penzin wrote:
On 7/15/19 10:28 AM, Claudio Jeker wrote:
On Sun, Jul 14, 2019 at 01:15:40PM +0300, Vadim Penzin wrote:
Since `sa_len' describes the size of a `sockaddr' (or one of its
derivatives
On 7/15/19 10:28 AM, Claudio Jeker wrote:
On Sun, Jul 14, 2019 at 01:15:40PM +0300, Vadim Penzin wrote:
Since `sa_len' describes the size of a `sockaddr' (or one of its
derivatives) /including/ `sa_len' (maybe I am wrong, but this is my
interpretation of the comment `total length
On 7/15/19 10:15 AM, Claudio Jeker wrote:
On Sun, Jul 14, 2019 at 05:28:17PM +0300, Vadim Penzin wrote:
The following patch replaces the hard-coded message size of 2048 bytes in
ifstated.c:rt_msg_handler() with RTM_MAXSIZE (which is currently defined as
2048 bytes) that, I believe
portmap(8) does not use setpassent(3) which is the only way of causing a
successful call to getpwnam(3) not to close the password database,
therefore the call to endpwent(3) seems to be unnecessary.
The following patch removes the call to endpwent(3):
Index: portmap.c
The following patch replaces the hard-coded message size of 2048 bytes
in ifstated.c:rt_msg_handler() with RTM_MAXSIZE (which is currently
defined as 2048 bytes) that, I believe, was the intent of the author.
Index: ifstated.c
===
Please find below a patch that contains the following:
(a) An explanation of alignment of address structures within a routing
message;
(b) An example (I admit, it is somewhat lengthy --- 146 lines) of a
basic parser of route(4) messages.
(This message is a follow-up to
Since `sa_len' describes the size of a `sockaddr' (or one of its
derivatives) /including/ `sa_len' (maybe I am wrong, but this is my
interpretation of the comment `total length' that appears near the
definition of `struct sockaddr' in ), `sa_len' just
cannot be zero.
Yes, it can not be zero.
I admit that I am not familiar with the release process of pre-built
binary packages; I might be writing to a wrong mailing list and I
apologize in advance.
All libtool scripts from qt5 (/usr/local/lib/qt5/*.la) contain the
following on their third line:
LIBQt5XXX_VERSION=5.9# The name
on line 1349
The first direct use of ROUNDUP that I quoted is on line 1431.
The second is on line 1476.
--Vadim
On 4/26/19 6:14 PM, Claudio Jeker wrote:
On Fri, Apr 26, 2019 at 01:55:52PM +0300, Vadim Penzin wrote:
Greetings,
1. The manual of route(4) explains the structure of its messages thus
Greetings,
1. The manual of route(4) explains the structure of its messages thus:
`Messages are formed by a header followed by a small number of
sockaddr structures (which are variable length), interpreted by
position, and delimited by the length entry in the sockaddr.'
(That
10 matches
Mail list logo
