Incorrect owner and group of isc_monitor1 file on linux's classic server [CORE1766]

[firebird-automations]

Submitted by: Yakov Hrebtov (jake)

Installation script of linux classic server creates isc_monitor1 file with the root owner and group. (user that runs installation procedure).
As a result, server cannot access this file, hence monitoring capabilities does not work.

The bug is caused by code in linux/classic/postinstall.sh.in and http://classiclibrary.sh.in.

This code from http://postinstall.sh.in creates and assings correct (firebird) owner on sc_init1 isc_lock1 isc_event1 files:

for i in isc\_init1 isc\_lock1 isc\_event1
  do
    FileName=$i\.\`hostname\`
    touch $FileName
  done

#⁠ Create log
touch firebird\.log


#⁠ Update ownership and SUID bits for programs\.
chown \-R $RunUser:$RunUser $FBRootDir

isc_monitor1 file is created next by code in function fixFilePermissions from http://classiclibrary.sh.in

for i in isc\_init1 isc\_lock1 isc\_event1 isc\_monitor1
do
    FileName=$i\.\`hostname\`
            touch $FileName
    chmod ug=rw,o= $FileName
done

This code is not correct as it does not change owner of touched isc_* files.
IMHO there should be only one place in code that creates all of isc_* files and assigns correct permissions to them.

[firebird-automations]

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

[firebird-automations]

Commented by: @AlexPeshkoff

fixed install scripts

[firebird-automations]

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 RC2 [ 10250 ]

Fix Version: 2.5 Alpha 1 [ 10224 ]

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test