Summary: | DAHTOOL-00065: modinfo dahdi fails when run from /etc on centos 5 | ||
Reporter: | Tzafrir Cohen (tzafrir) | Labels: | |
Date Opened: | 2013-12-30 10:37:48.000-0600 | Date Closed: | 2016-02-22 09:55:07.000-0600 |
Priority: | Minor | Regression? | |
Status: | Closed/Complete | Components: | General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Centos 5. Issue in modprobe seems to have been fixed in Centos 6. | Attachments: | |
Description: | The dahd init script may use the commands 'modinfo dahdi' or 'modprobe dahdi'.
Those commands will fail if the user is in a directory that has a subdirectory called 'dahdi'. My workaround is to try instead (cd /sys; modinfo dahdi) . But is /sys guaranteed to exist? I don't want to assume that the system will not have the directory /dahdi . Any better fix? | ||
Comments: | By: Russ Meyerriecks (rmeyerriecks) 2013-12-30 11:25:39.875-0600 Confirmed modinfo fails on centos 5.10 when run with in a directory with a subdirectory named 'dahdi'. [root@echo ~]# cd /etc/ [root@echo etc]# ls dahdi/ assigned-spans.conf.sample genconf_parameters init.conf modules span-types.conf.sample system.conf [root@echo etc]# modinfo dahdi modinfo: could not open dahdi: Is a directory [root@echo etc]# modinfo --version module-init-tools version 3.3-pre2 By: Russ Meyerriecks (rmeyerriecks) 2013-12-30 11:27:43.418-0600 modinfo manpage suggests that this is the expected behavior. By: Russ Meyerriecks (rmeyerriecks) 2013-12-30 11:31:56.210-0600 Works correctly in centos 6.2, modinfo chooses actual module first, instead of subdirectory. Tzafrir reported it working correctly in debian stable as well. By: Shaun Ruffell (sruffell) 2013-12-31 09:43:37.748-0600 What about just creating a temp directory in a subshell to be sure that there isn't a dahdi directory? Something like: (TEMP_DIR=$(mktemp -d -t) && cd $TEMP_DIR && modinfo dahdi; rm -f -r $TEMP_DIR) By: Tzafrir Cohen (tzafrir) 2016-02-22 09:55:07.852-0600 Why does an init script run from /etc ? I have not encountered this with the standard init script. Closing this issue as a solution was proposed and there has been no progress since. |