Standards Based Linux Instrumentation / Bugs / #2391 Client openlog changes settings

#2391 Client openlog changes settings

Milestone: Function

Status: pending-fixed

Owner: Michael Chase-Salerno

Labels: sfcb (1090)

Component:

Priority: 5

Updated: 2012-04-02

Created: 2012-03-15

Creator: Michael Chase-Salerno

Private: No

The fix for 3488688 removed the spawning of a logger thread for, usually short lived, clients. However, calling openlog when the client cim environment causes issues because it will change the loglevel that may have been set by the client.

openlog is completely optional according to the man page, so the call to startLogging for clients should just be removed.

LTC #79840

Discussion

Michael Chase-Salerno - 2012-03-15

CVS proposed patch

noopenlog.patch

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Chase-Salerno - 2012-03-15

assigned_to: buccella --> mchasal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Chase-Salerno - 2012-03-29

Committed to CVS head, needs to go into Git

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Chase-Salerno - 2012-04-02

git committed patch

0001-3505407-Client-openlog-changes-settings.patch

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Chase-Salerno - 2012-04-02

No longer call startLogging for sfcc local connect clients.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael Chase-Salerno - 2012-04-02

status: open --> pending-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Client openlog changes settings

Group

Searches

Help

#2391 Client openlog changes settings

Discussion