Liu Hua 86277395cf signal: do not print message when dealing with SIG_PIPE ...

If we print message when SIG_PIPE occuers in signal handler.
There is a loop {print->SIG_PIPE->print->SIG_PIPE...}, which consume
a lot of cpu time. So do not print message in this situaiton.

Signed-off-by: Liu Hua <weldonliu@tencent.com>

2021-01-12 12:34:53 +08:00

..

config_linux.go

Fix backwards compat with v2 containerd configs

2019-06-11 23:44:39 +00:00

config_unsupported.go

Fix backwards compat with v2 containerd configs

2019-06-11 23:44:39 +00:00

config_windows.go

Fix backwards compat with v2 containerd configs

2019-06-11 23:44:39 +00:00

config.go

Fix containerd config dump.

2019-10-23 22:38:18 -07:00

main_unix.go

signal: do not print message when dealing with SIG_PIPE

2021-01-12 12:34:53 +08:00

main_windows.go

Support NOTIFY_SOCKET

2020-03-07 10:24:51 -08:00

main.go

Allow configuration of different log formats: text, json

2020-12-04 13:12:41 -05:00

notify_linux.go

remove if condition because it is handled by the sdNotify daemon func

2020-04-26 23:18:34 +02:00

notify_unsupported.go

Support NOTIFY_SOCKET

2020-03-07 10:24:51 -08:00

oci-hook.go

update runc to v1.0.0-rc92

2020-08-06 20:31:33 +09:00

publish.go

vendor protobuf & grpc

2020-02-26 10:57:05 +09:00

service_unsupported.go

Word spelling correction

2019-09-25 16:49:54 +08:00

service_windows.go

Fix Windows service panic file to not be read-only

2020-11-24 01:37:00 -08:00