netdev - Re: RFC: pid "ownership" of ip config information

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1295778271.5657.7.camel@lat1>
Date:	Sun, 23 Jan 2011 11:24:31 +0100
From:	Patrick Schaaf <netdev@....de>
To:	Nicolas de Pesloüan 
	<nicolas.2p.debian@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: RFC: pid "ownership" of ip config information

On Fri, 2011-01-21 at 11:17 +0100, Nicolas de Pesloüan wrote:
> Le 21/01/2011 10:28, Patrick Schaaf a écrit :
> > The alternative to such a feature, would be to have an additional
> > monitoring process, which would watch the PID somehow, and need to
> > be configured to know what to withdraw when it dies.

> There exists some user space clustering system that should provide the same functionalities. Did you 
> had a look at http://www.linux-ha.org/ ?

Those would be the more complex instances of "an additional monitoring
process", right?

What happens when heartbeat is "kill -9"ed? Assume that I want to avoid
STOMITH like approaches.

My proposal could be _used_ by such complex clustering managers, too.

Or, did I overlook there a kernel based solution to "withdraw IP config
when processes die"? Can you provide a direct link on linux-ha?

best regards
  Patrick

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html