Assumptions about $ADTTMP
Hi,
I'm currently adding an autopkgtest to libcap2. In order for me to
properly test getting and setting capabilities on a sample executable
and subsequently verifying that is behaves as intended, I need access to
a filesystem mounted without the nosuid option. I realized this the hard
way by performing my tests in /tmp (which is mounted with nosuid here),
and wondering why I was getting EPERM all the time. The executable works
fine in a filesystem with default mount options.
That leads me to wonder: what can test developers safely assume about
$ADTTMP? Would it be possible, and make sense, to be more explicit about
its nature? filesystem type, mount options, a guarantee on the minimum
space available, etc.
Christian
Reply to: