Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What about 30_stop_selinux.onhold (two digit named script)? #1228

Closed
jsmeix opened this issue Mar 9, 2017 · 2 comments
Closed

What about 30_stop_selinux.onhold (two digit named script)? #1228

jsmeix opened this issue Mar 9, 2017 · 2 comments
Assignees
Labels
fixed / solved / done minor bug An alternative or workaround exists
Milestone

Comments

@jsmeix
Copy link
Member

jsmeix commented Mar 9, 2017

I found a two digit named script
backup/NETFS/GNU/Linux/30_stop_selinux.onhold
and I wonder how it came into the current ReaR master.

@gdha
I assign this issue to you because

git log -p --follow usr/share/rear/backup/NETFS/GNU/Linux/30_stop_selinux.onhold

shows that the script was renamed by you
from 30_stop_selinux.sh to 30_stop_selinux.onhold
in July 2011.
Currently I cannot explain why it was not renumbered.
Perhaps because its extension is not '.sh' but '.onhold'.

@jsmeix jsmeix added the minor bug An alternative or workaround exists label Mar 9, 2017
@jsmeix jsmeix added this to the Rear v2.1 milestone Mar 9, 2017
@gdha
Copy link
Member

gdha commented Mar 9, 2017

The script backup/NETFS/GNU/Linux/310_stop_selinux.sh is a symlink to backup/RSYNC/GNU/Linux/310_stop_selinux.sh and is exactly the same script as 30_stop_selinux.onhold
We better remove it.

@jsmeix
Copy link
Member Author

jsmeix commented Mar 9, 2017

@gdha
many thanks for your explanation and for your fast fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed / solved / done minor bug An alternative or workaround exists
Projects
None yet
Development

No branches or pull requests

2 participants