Re: [Pacemaker] Filesystem resource agent patch

2011-03-21 Thread Dejan Muhamedagic
On Mon, Mar 21, 2011 at 11:06:04AM +0100, Lars Ellenberg wrote: > On Mon, Mar 21, 2011 at 07:17:52AM +0100, Marko Potocnik wrote: > > Actually the symbolic link is the beautifier. We use different versions of > > database server and using the symbolic link mount point is always the same. > > > > D

Re: [Pacemaker] Filesystem resource agent patch

2011-03-21 Thread Lars Ellenberg
On Mon, Mar 21, 2011 at 07:17:52AM +0100, Marko Potocnik wrote: > Actually the symbolic link is the beautifier. We use different versions of > database server and using the symbolic link mount point is always the same. > > Do I need to do anything else for the patch to make it into the main branch

Re: [Pacemaker] Filesystem resource agent patch

2011-03-20 Thread Marko Potocnik
Actually the symbolic link is the beautifier. We use different versions of database server and using the symbolic link mount point is always the same. Do I need to do anything else for the patch to make it into the main branch? Regards, Marko On Fri, Mar 18, 2011 at 2:29 PM, Dejan Muhamedagic w

Re: [Pacemaker] Filesystem resource agent patch

2011-03-18 Thread Dejan Muhamedagic
Hi, On Fri, Mar 18, 2011 at 11:35:01AM +0100, Marko Potocnik wrote: > If you use symbolic links in Filesystem resource agent directory parameter, > then monitoring operation fails, because actual mount point in /proc/mounts > (or the output of mount command) is diferent as the configured one. Why

Re: [Pacemaker] Filesystem resource agent patch

2011-03-18 Thread Raoul Bhatia [IPAX]
On 03/18/2011 11:35 AM, Marko Potocnik wrote: > If you use symbolic links in Filesystem resource agent directory > parameter, then monitoring operation fails, because actual mount point > in /proc/mounts (or the output of mount command) is diferent as the > configured one. > > Here is the patch th

[Pacemaker] Filesystem resource agent patch

2011-03-18 Thread Marko Potocnik
If you use symbolic links in Filesystem resource agent directory parameter, then monitoring operation fails, because actual mount point in /proc/mounts (or the output of mount command) is diferent as the configured one. Here is the patch that fixes this: --- Filesystem_new_org 2011-03-18 11:32:3