phosphor-logging/phosphor-rsyslog-config, branch master

rsyslod: Change disable action

2019-05-27T05:25:06+00:00

This commit changes the way remote logging is disabled. Prior to this, we would create/delete the RSYSLOG_SERVER_CONFIG_FILE to enable/disable remote logging. Deleting the file would cause systemd to spin while it tried to trigger the syslog service via socket activation. So this commit reverts commits 40a7406097c0b5b0670c5987f6fe8c902d65562d and e165ea956c5557c2b470869d252c80744227b00f and then: To disable remote logging, we now simply ask that rsyslog ignore all incoming messages. This is done by using a special '~' rule for all messages. Tested: -- Verified that systemd no longer spins while trying to activate rsyslog with default config. -- Verified that setting a remote logging server over the REST API still works. Signed-off-by: Santosh Puranik Change-Id: Ife217a84395aaf32b775b7a84f85fc6310df3e7c

build: install into bin instead of sbin

2019-04-04T18:40:07+00:00

Installs into bin instead of sbin per guidelines Signed-off-by: Patrick Venture Change-Id: I382022b4f09374132cf07232177a5145c425f758

utils: restart: Fix restart bug

2019-04-03T18:16:19+00:00

bc89289f48ce5e1c8e5c66e657a176a0cd881d39 introduced a regression in the type signature of the RestartUnit call. The "replace" argument was accidentally deleted. Change-Id: I44313997b8b72b7163ad8b43ed2b45a01cb54e44 Signed-off-by: William A. Kennington III

utils: restart: Always restart service

2019-04-01T22:53:52+00:00

If the service has hit its reset limit in systemd, calling RestartUnit on the service will do nothing. This ensures that the service will try and restart at least once after a configuration change, regardless of whether or not it has failed in the past. Change-Id: I28962fc4ef9da641d1d19b8e09450e40d76e9c27 Signed-off-by: William A. Kennington III

Fix regression with e165ea9

2019-01-14T10:57:23+00:00

Commit e165ea9 introduces creation of the remote logging config file on demand, but it presumed the directory housing this config file pre-exists. That was not the case. Change-Id: I8974ce798de5d2747bcc4a67209f4d2c8081cfe6 Signed-off-by: Deepak Kodihalli

rsyslogd: don't start without actions

2019-01-11T12:53:33+00:00

Rsyslog is currently used only for remote logging. The daemon would run though (started by systemd) even when remote logging has not been configured. In other words, it would run without any actions. With Yocto 2.6, rsyslogd won't run without any actions. Hence, rsyslogd is now started only on the condition that the remote logging config file is present. Change-Id: Iae11d6912e60765ecb774b663d44b4e3c6f381a3 Signed-off-by: Deepak Kodihalli

add sdjournal interface to inject tests

2018-11-11T16:21:26+00:00

The goal of the tests is not to test phosphor-logging, but rather allow code to call through phosphor-logging/log<> during a test. Change-Id: Id8c84ded473decc7f9f0be268116083093f86e54 Signed-off-by: Patrick Venture

minor cleanup, std namespacing

2018-11-02T01:52:15+00:00

Added std namespace to places where there is a cpp version. Change-Id: I60a05a7c9cdcd79cfffc3c4968005fcbe34acf81 Signed-off-by: Patrick Venture

build: phosphor-rsyslog-config: drop invalid library

2018-10-31T16:24:20+00:00

The line in the makefile for including the phosphor-logging isn't populated during build in neither the CI nor the obmc-phosphor-image build. "phosphor_rsyslog_conf-server-conf.o -lsdbusplus -lsystemd -lphosphor_dbus" Tested: Verified CI still builds both. Tested: Verified the build line from the compile log doesn't populate that line with any value. Change-Id: I4ec8c44d6a717f011118826149e64d2dd2c56d52 Signed-off-by: Patrick Venture

add .clang-format

2018-10-27T01:16:27+00:00

Change-Id: I2c36b7886a25d0b235693b0776019d29608e1d52 Signed-off-by: Patrick Venture