Bug 825725
| Summary: | run_init always ends up with "execvp: No such file or directory" message | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Milos Malik <mmalik> |
| Component: | policycoreutils | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michal Trunecka <mtruneck> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 | CC: | dwalsh, ebenes, mgrepl, mtruneck |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | policycoreutils-2.2.5-6.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-13 12:56:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Milos Malik
2012-05-28 09:45:59 UTC
This bug blocks a lot of automated selinux-policy tests, which heavily use run_init. The bug is probably caused by this code in run_init.c:
417 if (execvp("/usr/sbin/open_init_pty", argv)) {
418 perror("execvp");
419 exit(-1);
420 }
421 return 0;
Because it calls open_init_pty, which was removed according to this line in changelog of policycoreutils:
* Wed Dec 21 2011 Dan Walsh <dwalsh> - 2.1.10-2
Remove open_init_pty
rpm -q policycoreutils
policycoreutils-2.1.11-18.fc18.x86_64
has
if (! access("/usr/sbin/open_init_pty", X_OK)) {
if (execvp(argv[1], argv + 1)) {
perror("execvp");
exit(-1);
}
return 0;
}
run_init requires full paths. run_init /sbin/service memcached status Although for this command it does blow up. with unconfined module disabled. run_init should die a painful death and is not really as needed in a systemd world. I think run_init should be dropped from the distribution, since systemd eliminates the need. That sound good. Removed in policycoreutils-2.1.13-26.el7 What was the fix, then? Seems the run_init is still there: # rpm -q policycoreutils policycoreutils-2.1.14-22.el7.x86_64 # rpm -ql policycoreutils | grep run_init /etc/pam.d/run_init /usr/sbin/run_init /usr/share/man/man8/run_init.8.gz /usr/share/man/ru/man8/run_init.8.gz I see that run_init is in policycoreutils-newrole now. Is there a reason to keep it in RHEL7 then or is it still going to be removed? policycoreutils-newrole-2.2.5-2.el7.x86_64 Ok, I am testing a fix. # rpm -ql policycoreutils-newrole /etc/pam.d/newrole /usr/bin/newrole /usr/share/man/man1/newrole.1.gz Easy fix (Makefile+specfile) but we will need to add an announcement about this change (a doc note). This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |