Menu

#1349 LOG : lgs_own_log_files is not called when logDataGroupname is reset to ""

future
invalid
nobody
None
defect
log
-
4.6 GA
minor
False
2017-11-16
2015-04-28
Srikanth R
No

Changeset : 6490

If the group name is set to tet using the following command, all the existing log files are owned by the new group.

immcfg -a logDataGroupname=tet logConfig=1,safApp=safLogService

Apr 28 10:01:14.035761 osaflogd [5213:lgs_imm.c:1988] >> config_ccb_apply_modify: CCB ID 9, 'logConfig=1,safApp=safLogService'
Apr 28 10:01:14.035766 osaflogd [5213:lgs_imm.c:1997] TR attribute logDataGroupname
Apr 28 10:01:14.035770 osaflogd [5213:lgs_imm.c:1948] >> logDataGroupname_fileown
Apr 28 10:01:14.035784 osaflogd [5213:lgs_imm.c:3123] NO LOG service data group is changed to tet
Apr 28 10:01:14.035791 osaflogd [5213:lgs_util.c:0606] >> lgs_own_log_files: stream safLgStrCfg=appstream1,safApp=safLogService
.....
Apr 28 10:01:14.036787 osaflogd [5213:lgs_filehdl.c:0757] T3 /var/log/opensaf/saflog/./saLogSystem_20150428_092511.log
Apr 28 10:01:14.036804 osaflogd [5213:lgs_filehdl.c:0771] << own_log_files_by_group_hdl

If the group name is set to default, the existing log files are not owned by calling lgs_own_log_files function.

immcfg -a logDataGroupname="" logConfig=1,safApp=safLogService

Apr 28 10:01:40.624851 osaflogd [5213:lgs_imm.c:1948] >> logDataGroupname_fileown
Apr 28 10:01:40.624875 osaflogd [5213:lgs_imm.c:3123] NO LOG service data group is changed to <Empty>
Apr 28 10:01:40.624884 osaflogd [5213:lgs_imm.c:1971] << logDataGroupname_fileown

Discussion

  • Anders Widell

    Anders Widell - 2015-11-02
    • Milestone: 4.4.2 --> 4.6.2
     
  • Mathi Naickan

    Mathi Naickan - 2016-05-04
    • Milestone: 4.6.2 --> 4.7.2
     
  • Anders Widell

    Anders Widell - 2016-09-20
    • Milestone: 4.7.2 --> 5.0.2
     
  • Anders Widell

    Anders Widell - 2017-04-03
    • Milestone: 5.0.2 --> future
     
  • Canh Truong

    Canh Truong - 2017-11-16
    • status: unassigned --> invalid
    • Blocker: --> False
     
  • Canh Truong

    Canh Truong - 2017-11-16

    From the log PR document, section 3.5.2.2:
    "After the deletion of the value of this attribute, the ownership of all current log files won't be changed and behavior will be kept as previous, i.e: new opened log file will be owned by the primary group as which LOG service is running. "

    So the group name of current log files are not changed for this case. lgs_own_log_files is not called.

     

Log in to post a comment.