[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[LDM #PNQ-433442]: LDM Question
- Subject: [LDM #PNQ-433442]: LDM Question
- Date: Wed, 22 May 2013 08:44:11 -0600
Hugh,
The problem with SELinux is that, by default, it prevents LDM programs from
logging to the LDM log file because, by default, it prevents the system logging
daemon from logging to any file that isn't under the /var/log directory -- and
the LDM log file is in the directory ~ldm/var/log.
One might be able to work around this via symbolic links, but because that
would defeat the intention of the default SELinux policy rule, I would not be
surprised if that didn't work.
Unfortunately, I haven't investigated the matter sufficiently to devise an
SELinux policy rule that would allow LDM logging. I intend to, but it's a
question of time. If you arrive at a solution, please let me know.
> To whomever it may concern,
>
>
>
> I have recently been asked to try and edit our SELinux policy module in
> order to enforce SELinux while at the same time allowing LDM to
> function. The only catch to this is knowing what in SELinux specifically
> breaks LDM. Can you provide me info on this? For instance what policy to
> edit in order to allow LDM to function properly. Thanks.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Dave Hardy
>
> CSSI, Inc.
> SPAWAR Office of Polar Programs
> Charleston Naval Weapon Station
> Systems Administrator
> Office: 843-218-3007
>
> Cell: 912-856-3334
>
> address@hidden
> <https://owa.cssiinc.com/owa/redir.aspx?C=bf97cdba659846b5bf5b7e007ba399
> 5c&URL=mailto%3ahhardy%40cssiinc.com>
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: PNQ-433442
Department: Support LDM
Priority: Normal
Status: Closed