[
https://issues.apache.org/jira/browse/CLOUDSTACK-9551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-9551:
-------------------------------------------
Summary: Pull KVM agent's tmp folder usage within its own folder structure
(was: Pull KVM agent's tmp folder urage within its own folder structure)
> Pull KVM agent's tmp folder usage within its own folder structure
> -----------------------------------------------------------------
>
> Key: CLOUDSTACK-9551
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9551
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.1, 4.7.1, 4.9.1.0
> Reporter: Abhinandan Prateek
> Assignee: Abhinandan Prateek
>
> We ran into an issue today where the sysadmins wanted to put /tmp on its own
> mount and set the "noexec" mount flag as a security measure. This is
> incompatible with the CloudStack KVM agent, because it stores JNA tmp files
> here and Java is unable to map into these objects. To get around this we
> moved the agent's temp dir to live with the agent files, which seems like a
> reasonable thing to do regardless of whether you're trying to secure /tmp.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
