On Sat Apr 14 12, Jeremie Le Hen wrote:
> On Sat, Apr 14, 2012 at 08:59:42AM -0400, Robert Huff wrote:
> >
> > > This is probably a sysctl handler that is causing the reboot. You can
> > > run this one-liner to spot the culprit (use sh):
> > >
> > > for i in $(sysctl -Na); do sysctl $i >
On Sat, Apr 14, 2012 at 08:59:42AM -0400, Robert Huff wrote:
>
> > This is probably a sysctl handler that is causing the reboot. You can
> > run this one-liner to spot the culprit (use sh):
> >
> > for i in $(sysctl -Na); do sysctl $i >> ~/sysctl.out; sync; done
> >
> > Each sysctl wi
Jeremie Le Hen writes:
> This is probably a sysctl handler that is causing the reboot. You can
> run this one-liner to spot the culprit (use sh):
>
> for i in $(sysctl -Na); do sysctl $i >> ~/sysctl.out; sync; done
>
> Each sysctl will be called in turn and the output is appended to
Hi Alexander,
On Fri, Apr 13, 2012 at 09:36:44PM +, Alexander Best wrote:
>
> i'm running HEAD on amd64 and experienced some really annoying resets during
> the last couple of months.
>
> when i do 'sysctl -a' or 'sysctl -a|grep bla', my whole system does a hard
> reset. no core dump gets pr
Am 04/13/12 23:36, schrieb Alexander Best:
> hi there,
>
> i'm running HEAD on amd64 and experienced some really annoying resets during
> the last couple of months.
>
> when i do 'sysctl -a' or 'sysctl -a|grep bla', my whole system does a hard
> reset. no core dump gets produced.
>
> isn't there
hi there,
i'm running HEAD on amd64 and experienced some really annoying resets during
the last couple of months.
when i do 'sysctl -a' or 'sysctl -a|grep bla', my whole system does a hard
reset. no core dump gets produced.
isn't there a way to find out which sysctl variable is causing the reset
