See the following output:

# strings /usr/lib64/security/pam_timestamp.so | grep /run/
/var/run//pam_timestamp
/var/run//pam_timestamp/_pam_timestamp_key

Thanks. But it would be better to use the original approach used in the original test from @mmalik

TIMESTAMP_DIR=${TIMESTAMP_DIR:-"/run//pam_timestamp"}

I though it's a typo a dropped double // I'm sorry it's my fault.

Btw you could make sed command readable using other separater than /:

sed "s|run//|run/|"

Thanks. But it would be better to use the original approach used in the original test from @mmalik
TIMESTAMP_DIR=${TIMESTAMP_DIR:-"/run//pam_timestamp"}

I though it's a typo a dropped double // I'm sorry it's my fault.

In that case when changing it back please don't forget to add a comment explaining why the double slash is needed, so that we don't repeat history again ;)

@zpytela Thanks again for the reporting and sorry for the complication. I've created a new PR with @mmalik 's original approach - https://src.fedoraproject.org/tests/selinux/pull-request/64

@zpytela please update the sed command in order not to use unnecessary escape \

Maybe it would be enough to use just sed 's|//|/|'

While we are at it, we could make it even more robust and replace all consecutive slashes with just one: sed 's|//*|/|g'

I changed the expressions to make the command more readable for majority of readers. (Personally, I am used to reading those ugly ones.

I've added a comment why sed is needed and merged. Thanks!

https://src.fedoraproject.org/tests/selinux/c/f1a42a48f9ac874e2f53e801429c3c91f0654a39?branch=master