‐‐‐ Original Message ‐‐‐
On Thursday, January 31, 2019 11:31 PM, Alexander Bluhm
wrote:
> On Thu, Jan 31, 2019 at 04:26:45PM -0500, Ted Unangst wrote:
>
> > Instead, we note that the write failed and mark a flag in the vnode. Future
> > calls to fsync will then return EIO when this fla
Use an It tag to label the additional steps referred to at the beginning
of step 2:
"This step, as well as the next one, needs to be done for every peer.
Furthermore the last step will need to be done once for each ID you want
the peer to have"
Change the file name passed to openssl for extfile to
On Fri, Feb 15, 2019 at 03:07:15PM +0100, Claudio Jeker wrote:
> Another diff to ease portability of bgpd. The sa_len field in struct
> sockaddr does not exist on Linux so instead of using it pass a length to
> the function (e.g. like bind(2) and connect(2) and do the same when
> passing around str
Alexander Bluhm wrote:
> We should not implement the magic which device allows fsync(2) into
> dd(1). Just do what the user says, if it is nonsense, give him an
> error.
sure. ok.
On 13.02.2019 15:08, Martin Pieuchot wrote:
+ val = rwlock->value;
+ if (val == UNLOCKED || (val & WAITING))
+ break;
+
+ SPIN_WAIT();
+ }
+
+ while ((error = _rthread_rwlock_tryrdlock(rwlock)) == EBUSY) {
+
On Fri, Feb 15, 2019 at 07:58:48PM +0100, Giovanni Bechis wrote:
> ping...
> any possible issue with millert@ diff ?
> Giovanni
>
> On Sun, Oct 07, 2018 at 08:35:28PM -0600, Todd C. Miller wrote:
> > On Sun, 07 Oct 2018 17:08:06 +0200, Marc Espie wrote:
> >
> > > Specifically, the only part that
ok
Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.02.15 15:07:15 +0100:
> Another diff to ease portability of bgpd. The sa_len field in struct
> sockaddr does not exist on Linux so instead of using it pass a length to
> the function (e.g. like bind(2) and connect(2) and do the same when
> passing
ok
Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.02.15 12:01:20 +0100:
> To make bgpd more portable it is better to move all the link state code
> into kroute.c. Especially for something as simple as a single up / down
> flag. This is doing that and removes the net/if_types.h include from
> ses
ping...
any possible issue with millert@ diff ?
Giovanni
On Sun, Oct 07, 2018 at 08:35:28PM -0600, Todd C. Miller wrote:
> On Sun, 07 Oct 2018 17:08:06 +0200, Marc Espie wrote:
>
> > Specifically, the only part that cares about
> > locale is sort, and it's definitely correct in fixing
> > it's n
Another diff to ease portability of bgpd. The sa_len field in struct
sockaddr does not exist on Linux so instead of using it pass a length to
the function (e.g. like bind(2) and connect(2) and do the same when
passing around struct sockaddr_storage in the listener case.
The remaining sa_len, sin_le
On Fri, Feb 15, 2019 at 11:55:59AM +0100, Oleg Pahl wrote:
> Hi @all,
>
> Is it ok, that on man page *PKG_SIGN(1)* there is*[-D name=[value]]*
> argument,
>
> but there is no info about value of arg. below ... (I mean what kind of
> value's is possible to use with -D)
>
> I think, that its will
On Fri, Feb 15, 2019 at 01:28:15PM +0100, Alexander Bluhm wrote:
> We should not implement the magic which device allows fsync(2) into
> dd(1). Just do what the user says, if it is nonsense, give him an
> error.
Seems reasonable to me.
> > I know this wording is similar to fsync(2), but I think I
On Thu, Feb 14, 2019 at 05:20:13PM -0500, Ted Unangst wrote:
> What does gnu dd do if the output is stdout? Is it an error?
On Linux it fails with an error.
linux$ yes | dd count=4 bs=1 conv=fsync
y
y
dd: fsync failed for 'standard output': Invalid argument
4+0 records in
4+0 records out
4 bytes
To make bgpd more portable it is better to move all the link state code
into kroute.c. Especially for something as simple as a single up / down
flag. This is doing that and removes the net/if_types.h include from
session.c. Result should be the same just computation is moved.
OK?
--
:wq Claudio
Hi @all,
Is it ok, that on man page *PKG_SIGN(1)* there is*[-D name=[value]]*
argument,
but there is no info about value of arg. below ... (I mean what kind of
value's is possible to use with -D)
I think, that its will be better to put this Info on man page. Not just
for me =)
Many thx f
On Fri, Feb 15, 2019 at 11:19:57AM +0100, Oleg Pahl wrote:
> Hi @all,
>
> Today I try to work with man pages using *vim*.
>
> *# man man | vim -*
>
> why i see raw (a lot of special char.) data by default? is it ok?
>
> *# ma man | less *
>
> I see no special characters. looks very good.
>
>
Perfect !
Thanks all !
On 2/15/19 11:35 AM, Otto Moerbeek wrote:
On Fri, Feb 15, 2019 at 11:19:57AM +0100, Oleg Pahl wrote:
Hi @all,
Today I try to work with man pages using *vim*.
*# man man | vim -*
why i see raw (a lot of special char.) data by default? is it ok?
*# ma man | less *
I
On Fri, Feb 15, 2019 at 11:19:57AM +0100, Oleg Pahl wrote:
> Hi @all,
>
> Today I try to work with man pages using *vim*.
>
> *# man man | vim -*
>
> why i see raw (a lot of special char.) data by default? is it ok?
>
> *# ma man | less *
>
> I see no special characters. looks very good.
>
>
On 2/15/19 11:19 AM, Oleg Pahl wrote:
> Hi @all,
>
> Today I try to work with man pages using *vim*.
What do you mean with work with? Do you mean you want to edit them, or
you want to read them?
If you want to edit them, just edit the source
/usr/src/usr.bin/mandoc/man.1 (you need to have a local
Hi @all,
Today I try to work with man pages using *vim*.
*# man man | vim -*
why i see raw (a lot of special char.) data by default? is it ok?
*# ma man | less *
I see no special characters. looks very good.
Is it possible to convert *raw* data of man page to normal format (for
*vim*) with
On Thu, Feb 14, 2019 at 4:21 PM Ted Unangst wrote:
> Alexander Bluhm wrote:
> > GNU dd has the conv=fsync feature which does an fsync(2) after final
> > write to output. I find this useful for write performance measurement
> > through the file system without buffer cache optimization. Others
>
21 matches
Mail list logo
