[OpenAFS] Re: odd problem with RW site after a botched replica
Timothy Balcer
timothy@telmate.com
Tue, 30 Oct 2012 21:53:56 -0700
--047d7b450180a5e4eb04cd53b067
Content-Type: text/plain; charset=ISO-8859-1
Huh.. per O'Reilly:
"The kernel uses the SIGTERM signal to inform the target process that it
should stop."
http://linuxdevcenter.com/pub/a/linux/2006/11/30/linux-out-of-memory.html?page=2
Is that out of date?
On Tue, Oct 30, 2012 at 8:19 PM, Brandon Allbery <allbery.b@gmail.com>wrote:
> On Tue, Oct 30, 2012 at 11:14 PM, Timothy Balcer <timothy@telmate.com>wrote:
>
>> The OOM killer *is* the kernel, so the AFS logs just know it's dead,
>>
>>> not that the kernel
>>> decided "heeeey...."
>>>
>>
>> Yeah.. I knew that ;-) What I was suggesting was that upon receiving the
>> signal, salvager didn't note that fact in the Salvage log. You could trap
>> SIGTERM, and log it on the way out, no?
>>
>
> The kernel's OOM killer sends SIGKILL, which cannot be trapped or ignored.
>
> --
> brandon s allbery kf8nh sine nomine
> associates
> allbery.b@gmail.com
> ballbery@sinenomine.net
> unix/linux, openafs, kerberos, infrastructure
> http://sinenomine.net
>
>
--
Timothy Balcer / IT Services
Telmate / San Francisco, CA
Direct / (415) 300-4313
Customer Service / (800) 205-5510
--047d7b450180a5e4eb04cd53b067
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Huh.. per O'Reilly:<br><br>"The kernel uses the <code>SIGTERM</cod=
e> signal to inform the target process that it should stop."<br><br><a=
href=3D"http://linuxdevcenter.com/pub/a/linux/2006/11/30/linux-out-of-memo=
ry.html?page=3D2">http://linuxdevcenter.com/pub/a/linux/2006/11/30/linux-ou=
t-of-memory.html?page=3D2</a><br>
<br>Is that out of date?<br><br><div class=3D"gmail_quote">On Tue, Oct 30, =
2012 at 8:19 PM, Brandon Allbery <span dir=3D"ltr"><<a href=3D"mailto:al=
lbery.b@gmail.com" target=3D"_blank">allbery.b@gmail.com</a>></span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Tue, O=
ct 30, 2012 at 11:14 PM, Timothy Balcer <span dir=3D"ltr"><<a href=3D"ma=
ilto:timothy@telmate.com" target=3D"_blank">timothy@telmate.com</a>></sp=
an> wrote:<br>
</div><div class=3D"gmail_quote"><div class=3D"im"><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
<div>The OOM killer *is* the kernel, so the AFS logs just know it's dea=
d,<br></div><div class=3D"gmail_quote"><div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
not that the kernel<br>
decided "heeeey...."<span><font color=3D"#888888"><br></font></sp=
an></blockquote></div><div><br>Yeah.. I knew that ;-) What I was suggesting=
was that upon receiving the signal, salvager didn't note that fact in =
the Salvage log. You could trap SIGTERM, and log it on the way out, no?</di=
v>
</div></blockquote><div><br></div></div><div>The kernel's OOM killer se=
nds SIGKILL, which cannot be trapped or ignored.</div><span class=3D"HOEnZb=
"><font color=3D"#888888"><div><br></div></font></span></div><span class=3D=
"HOEnZb"><font color=3D"#888888">-- <br>
<div dir=3D"ltr"><div>brandon s allbery kf8nh =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 sine nomine associates</div>
<div><a href=3D"mailto:allbery.b@gmail.com" target=3D"_blank">allbery.b@gma=
il.com</a> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0<a href=3D"mailto:ballbery@sinenomine.net" target=3D"_blank">ballbery@si=
nenomine.net</a></div><div>unix/linux, openafs, kerberos, infrastructure =
=A0 =A0 =A0 =A0 =A0<a href=3D"http://sinenomine.net" target=3D"_blank">http=
://sinenomine.net</a></div>
</div><br>
</font></span></div>
</blockquote></div><br><br clear=3D"all"><br>-- <br><span style=3D"border-c=
ollapse:collapse;color:rgb(102,102,102);font-family:verdana,sans-serif;font=
-size:x-small">Timothy Balcer / IT Services<br>Telmate / San Francisco, CA<=
br>
Direct / </span><span style=3D"border-collapse:collapse;font-family:verdana=
,sans-serif;font-size:x-small"><font color=3D"#1155cc">(415) 300-4313</font=
><br><font color=3D"#666666">Customer Service /=A0</font><a value=3D"+18002=
055510" style=3D"color:rgb(17,85,204)">(800) 205-5510</a></span><br>
--047d7b450180a5e4eb04cd53b067--