I am in a similar situation (pppoe sessions restarts, although my IP addresses
do not change), and I needed to re-add the default IPv6 route after completion
of IPv6CP. Note that there are several layers involved (link, IPv4, IPv6), I
would guess that for pppoe "link is up" would mean LCP
My DSL connection, using a modem in "bridge" mode and pppoe(4), suffers
from disconnections every few (5 or so) days. The following message is
printed in the syslog:
pppoe0: LCP keepalive timeout
which indicates that several Echo-Requests were not followed by replies,
so the kernel considers
.
On Sun, Nov 25, 2018 at 09:04:22PM -0800, Philip Guenther wrote:
> On Fri, Nov 23, 2018 at 1:51 PM Olivier Taïbi wrote:
>
> > Sorry about the wrong report, I just tested again and I can see the same
> > behaviour with OpenBSD 6.4: sending SIGTERM to the sh process after
> >
:50:29AM +0100, Olivier Taïbi wrote:
> After some testing, this issue does not seem to be directly caused by
> ksh. Compiling ksh from a year ago, I get the same behaviour: SIGTERM is
> not passed on to child. I'm not sure what to try next. Bisecting
> /usr/src?
>
> On Fri, Nov 23,
After some testing, this issue does not seem to be directly caused by
ksh. Compiling ksh from a year ago, I get the same behaviour: SIGTERM is
not passed on to child. I'm not sure what to try next. Bisecting
/usr/src?
On Fri, Nov 23, 2018 at 08:55:16AM +0100, Olivier Taïbi wrote:
> On Thu, Nov
On Thu, Nov 22, 2018 at 05:14:38PM -0800, Philip Guenther wrote:
> On Thu, Nov 22, 2018 at 3:08 PM Olivier Taïbi wrote:
>
> > It seems that non-interactive sh(1) (i.e. sh -c command or sh file)
> > ignores the TERM signal. I'm surprised, is this the intended behaviour?
>
It seems that non-interactive sh(1) (i.e. sh -c command or sh file)
ignores the TERM signal. I'm surprised, is this the intended behaviour?
The man page says that interactive shells will ignore SIGTERM, but does
not mention the non-interactive case.
7 matches
Mail list logo
