Hi,
the last few days i basically dug in to focus on understanding the vi
editing mode in ksh(1). Given the quick partial success with the emacs
mode, i hoped that the usual 20/80 rule might apply. However, the code
implementing vi mode seems substantially more contorted to me than the
code impl
On Sun, 27 Dec 2015, Stuart Henderson wrote:
> Widening the audience to tech in case anyone with an idea missed it on
> ports: it seems some people are having a lot more trouble than just
> needing to restart build 2 or 3 times.
...
> To replicate
>
> cd /usr/ports/x11/vlc
> make fake
> cd /usr/
On Sat, Jan 16, 2016 at 10:04:56AM -0700, Todd C. Miller wrote:
> On Sat, 16 Jan 2016 14:56:48 +0100, Landry Breuil wrote:
>
> > Good point - the other option would be to log_warn() ? Or just call
> > unlink() without checking the return code like its' done for csockpath ?
>
> I think (void)unlin
On Sat, 16 Jan 2016 14:56:48 +0100, Landry Breuil wrote:
> Good point - the other option would be to log_warn() ? Or just call
> unlink() without checking the return code like its' done for csockpath ?
I think (void)unlink(...) is fine for cleanup.
- todd
On Sat, Jan 16, 2016 at 11:15:30PM +1000, Jonathan Matthew wrote:
> On Sat, Jan 16, 2016 at 12:19:18PM +0100, Landry Breuil wrote:
> > On Sat, Jan 16, 2016 at 11:47:33AM +0100, Landry Breuil wrote:
> > > On Sat, Jan 16, 2016 at 11:40:35AM +0100, Landry Breuil wrote:
> > > > Hi,
> > > >
> > > > pla
I use the following script to reload pf rules. It allows me to check
that what I wrote was interpreted as I intended:
#!/bin/sh
test "$(id -u)" -eq 0 || exec sudo -- "$0" "$@"
old=$(mktemp /tmp/pf-reload.) || exit
trap "rm $old" EXIT
pfctl -sr > $old || exit
pfctl -f /etc/pf.conf; rc=$?
On Sat, Jan 16, 2016 at 12:19:18PM +0100, Landry Breuil wrote:
> On Sat, Jan 16, 2016 at 11:47:33AM +0100, Landry Breuil wrote:
> > On Sat, Jan 16, 2016 at 11:40:35AM +0100, Landry Breuil wrote:
> > > Hi,
> > >
> > > playing with ldapd, i noticed that upon exit, the child process (ldape)
> > > is
On Sat, Jan 16, 2016 at 11:47:33AM +0100, Landry Breuil wrote:
> On Sat, Jan 16, 2016 at 11:40:35AM +0100, Landry Breuil wrote:
> > Hi,
> >
> > playing with ldapd, i noticed that upon exit, the child process (ldape)
> > is aborted by pledge:
> >
> > ldapd(10229): syscall 10 "cpath"
> >
> > and /
On Sat, Jan 16, 2016 at 11:40:35AM +0100, Landry Breuil wrote:
> Hi,
>
> playing with ldapd, i noticed that upon exit, the child process (ldape)
> is aborted by pledge:
>
> ldapd(10229): syscall 10 "cpath"
>
> and /var/run/ldapi / ldapd.sock are left behind.
>
> ktracing and looking at the code
Hi,
playing with ldapd, i noticed that upon exit, the child process (ldape)
is aborted by pledge:
ldapd(10229): syscall 10 "cpath"
and /var/run/ldapi / ldapd.sock are left behind.
ktracing and looking at the code, it seems control_cleanup in
control.c:117 tries to unlink the control socket, and
10 matches
Mail list logo