In mandocdb.c it appears cmp(1) and rm(1) are executed in a child
process. It seems that if the logic from these programs were duplicated
the pledge in mandocdb.c could be further restricted and even not bother
with forking.
Would such a change be pointless churn however? Both cmp(1) and rm(1)
are
Thank you for the replies Ingo and the diffs!
George Brown
On 26 August 2017 at 17:04, Ingo Schwarze wrote:
> Hi George,
>
> George Brown wrote on Thu, Aug 24, 2017 at 02:01:05PM +0100:
>
>> In mandocdb.c it appears cmp(1) and rm(1) are executed in a child
>> proce
I can reproduce this after updating to the Sept 18th snapshot, I did not
observe this on my Aug 20 snapshot install if that aids in narrowing
down when this was introduced.
I suspect reporting this to bugs rather than misc may be a better course
of action.
https://www.openbsd.org/report.html
On
There's ifstated - http://man.openbsd.org/ifstated
On 21 September 2017 at 14:29, Krzysztof Strzeszewski wrote:
> Hi,
>
> How to log up or down (connect or not connect cable) interface end change
> physical address on OpenBSD?
>
>
> --
> Regards,
> Krzysztof Strzeszews
It appears in handling SIGCHLD if the child is stopped due to SIGTSTP
or SIGSTOP then it is continued. Indeed screen appears to do the same.
Could someone kindly explain to me why this is done?
I ask as dvtm (another terminal multiplexer) hits an issue on MacOS
where what would be called "panes" i
It seems this ELF note was used for the now dead compat_linux feature.
Aside from compat systems in other operating systems that may wish to
identify OpenBSD binaries does this note have any other active uses?
Thank you for the reply, I was just curious.
On Thu, 27 May 2021 at 04:21, Philip Guenther wrote:
>
> On Fri, May 21, 2021 at 5:28 AM George Brown <321.geo...@gmail.com> wrote:
>>
>> It seems this ELF note was used for the now dead compat_linux feature.
>> Asid
7 matches
Mail list logo
