Re: [ClusterLabs] multiple action= lines sent to STDIN of fencing agents - why?

2015-10-19 Thread Marek marx Grác
Hi, On 15 October 2015 at 16:45:58, Jan Pokorný (jpoko...@redhat.com) wrote: > On 15/10/15 12:25 +0100, Adam Spiers wrote: > > I inserted some debugging into fencing.py and found that stonithd > > sends stuff like this to STDIN of the fencing agents it forks: > > > > action=list > > param1=value1

Re: [ClusterLabs] multiple action= lines sent to STDIN of fencing agents - why?

2015-10-15 Thread Ken Gaillot
On 10/15/2015 06:25 AM, Adam Spiers wrote: > I inserted some debugging into fencing.py and found that stonithd > sends stuff like this to STDIN of the fencing agents it forks: > > action=list > param1=value1 > param2=value2 > param3=value3 > action=list > > where paramX and va

Re: [ClusterLabs] multiple action= lines sent to STDIN of fencing agents - why?

2015-10-15 Thread Jan Pokorný
On 15/10/15 12:25 +0100, Adam Spiers wrote: > I inserted some debugging into fencing.py and found that stonithd > sends stuff like this to STDIN of the fencing agents it forks: > > action=list > param1=value1 > param2=value2 > param3=value3 > action=list > > where paramX and v

[ClusterLabs] multiple action= lines sent to STDIN of fencing agents - why?

2015-10-15 Thread Adam Spiers
I inserted some debugging into fencing.py and found that stonithd sends stuff like this to STDIN of the fencing agents it forks: action=list param1=value1 param2=value2 param3=value3 action=list where paramX and valueX come from the configuration of the primitive for the fenci