Summary: | sys-apps/openrc runscript does not parse symlinks correctly if the target starts with "./" | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | vm |
Component: | OpenRC | Assignee: | OpenRC Team <openrc> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | dmitry_b, infra-bugs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | 0001-fix-handling-of-symbolic-links-in-init.d-directory.patch |
Description
vm
2011-05-04 13:19:34 UTC
*** This bug has been marked as a duplicate of bug 350910 *** *** Bug 366819 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 350910 *** I do not see this as a duplicate of #350910. Basically, if a symbolic link links to something in the current directory, we should be able to resolve that, but it doesn't do anything about the other issue. That's related to the other bug and to my patch. It should be fixed in git already. Symlink handling in general was/is? broken, both bugs are related to the same part of code. Created attachment 280657 [details]
0001-fix-handling-of-symbolic-links-in-init.d-directory.patch
All,
I've thought about this quite a bit and I think the best way to go is to
enforce the requirement from this comment in the openrc source code:
/* We need to work out the real full path to our service.
* This works fine, provided that we ONLY allow multiplexed services
* to exist in the same directory as the master link.
* Also, the master link as to be a real file in the init dir. */
The attached patch does this. What do you think about going this route?
Works for me. All, after further discussion with robbat2 on irc yesterday, I believe that fixing bug #350910 will fix this as a side effect. It is technically not a duplicate, but it seems that marking this as a duplicate and moving all of the work to the other bug will be the easiest way to track this. *** This bug has been marked as a duplicate of bug 350910 *** |