> On Jul 4, 2020, at 8:59 AM, Enji Cooper <yaneurab...@gmail.com> wrote:
> 
>> 
>> On Jul 2, 2020, at 7:57 PM, Enji Cooper <yaneurab...@gmail.com 
>> <mailto:yaneurab...@gmail.com>> wrote:
>> 
>>> 
>>> On Jun 29, 2020, at 10:26 AM, Gordon Bergling <g...@freebsd.org 
>>> <mailto:g...@freebsd.org>> wrote:
>>> 
>>> Hi,
>>> 
>>> I recently stumbled across undeletable files that are generated by kyua 
>>> test runs,
>>> for example
>>> 
>>> -rwxr-xr-x  1 root  wheel  0 May  9 13:10 
>>> /tmp/kyua.aB4q62/8676/work/fileforaudit
>>> 
>>> I haven't yet identified the test that generate those files, but it is 
>>> impossible
>>> to delete them. I have clear_tmp_enable="YES" set in the /etc/rc.conf, but 
>>> on every boot the system argues that these file aren't deletable. 
>>> I tried to 'rm -rf' them by hand but, even this wasn't possible. I have 
>>> looked for
>>> any extend attributes, but I didn't find any.
>>> 
>>> Has anyone an idea how this is possible and may how these files can be 
>>> deleted?
>> 
>> The issue is tests/sys/audit/file-attribute-modify.c , based on the file 
>> present that can’t be deleted. Can you please provide more information about 
>> the test run in a PR (I see how it can leave files behind, but I want to 
>> make sure it is what I think it is, first)?
> 
>       PR filed: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247761 
> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247761> . Working on a CR.

Hi,
        I just created the following CR: https://reviews.freebsd.org/D25561 
<https://reviews.freebsd.org/D25561> and added the following related GitHub 
issue to PR: https://github.com/jmmv/kyua/issues/142 
<https://github.com/jmmv/kyua/issues/142> . This should be completed to avoid 
issues like this in the future from occurring.
Thank you for the report!
-Enji
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to