oslo.privsep - en to en_GB translation catalogue (6 entries)

en: Add ``timeout`` as parameter to ``PrivContext`` and add ``entrypoint_with_timeout`` decorator to cover the issues with commands which take random time to finish. ``PrivsepTimeout`` is raised if timeout is reached.
en_GB: Add ``timeout`` as a parameter to ``PrivContext`` and add ``entrypoint_with_timeout`` decorator to cover the issues with commands which take random time to finish. ``PrivsepTimeout`` is raised if a timeout is reached.

en: By default all contexts use ``oslo_privsep.daemon``, but in some cases we may need finer grained log levels, for example nova running in debug mode could log its own privsep calls on INFO level regardless, but leave all libraries' privsep calls, such as os-brick's, to be logged in the normal DEBUG level.
en_GB: By default all contexts use ``oslo_privsep.daemon``, but in some cases, we may need finer-grained log levels, for example, Nova running in debug mode could log its own privsep calls on INFO level regardless, but leave all libraries' privsep calls, such as os-brick's, to be logged in the normal DEBUG level.

en: Privsep now uses multithreading to allow concurrency in executing privileged commands. The number of concurrent threads defaults to the available CPU cores, but can be adjusted by the new ``thread_pool_size`` config option.
en_GB: Privsep now uses multithreading to allow concurrency in executing privileged commands. The number of concurrent threads defaults to the available CPU cores but can be adjusted by the new ``thread_pool_size`` config option.

en: Switch to reno for managing release notes.
en_GB: Switch to Reno for managing release notes.

en: When the privsep helper dies, the client side PrivContext now restarts the client channel and the helper so that privileged commands can continue to be processed. See `bug 1715374`_ for details. In conjunction with the fix for `bug 1794708`_ in oslo.service, the nova-compute service now behaves correctly when  it receives ``SIGHUP``.
en_GB: When the privsep helper dies, the client side PrivContext now restarts the client channel and the helper so that privileged commands can continue to be processed. See `bug 1715374`_ for details. In conjunction with the fix for `bug 1794708`_ in oslo.service, the nova-compute service now behaves correctly when it receives ``SIGHUP``.

en: ``Warning``: The daemon (the root process) task won't stop when timeout is reached. That means we'll have less available threads if the related thread never finishes.
en_GB: ``Warning``: The daemon (the root process) task won't stop when the timeout is reached. That means we'll have fewer available threads if the related thread never finishes.
