Project

General

Profile

Feature #4898

Allow packages to request syslogd socket to be created inside chroot

Added by Paul K almost 2 years ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Category:
Logging
Target version:
Start date:
07/28/2015
Due date:
% Done:

100%


Description

Currently there is no way to run a package inside chroot if it requires logging socket to be located inside chroot. Like what's being currently done for dhcpd.

Associated revisions

Revision ab31acb9
Added by k-paulius over 1 year ago

Allow packages to request syslogd log socket to be created inside chroot by specifying it in /package/logging/logsocket element. Implements #4898.

Example:
<package>
<logging>
<logsocket>/var/appname/var/run/log</logsocket>
</logging>
</package>

Revision 7066f0cc
Added by k-paulius 8 months ago

Allow packages to request syslogd log socket to be created inside chroot by specifying it in /package/logging/logsocket element. Implements #4898.

Example:
<package>
<logging>
<logsocket>/var/appname/var/run/log</logsocket>
</logging>
</package>

(cherry picked from commit ab31acb937792bdedef11fcdbd1d98ad126ebc0b)

History

#2 Updated by Anonymous 8 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#3 Updated by Renato Botelho 8 months ago

  • Assignee set to Renato Botelho
  • Target version set to 2.4.0

#4 Updated by Jim Pingle 3 months ago

  • Target version changed from 2.4.0 to 2.3.3

#5 Updated by Renato Botelho 3 months ago

  • Status changed from Feedback to Resolved

works (haproxy for instance)

Also available in: Atom PDF