[asterisk-bugs] [JIRA] (DAHTOOL-65) modinfo dahdi fails when run from /etc on centos 5

[Russ Meyerriecks (JIRA)]

    [ https://issues.asterisk.org/jira/browse/DAHTOOL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213362#comment-213362 ] 

Russ Meyerriecks commented on DAHTOOL-65:
-----------------------------------------

Confirmed modinfo fails on centos 5.10 when run with in a directory with a subdirectory named 'dahdi'.

[root at echo ~]# cd /etc/
[root at echo etc]# ls dahdi/
assigned-spans.conf.sample  genconf_parameters  init.conf  modules  span-types.conf.sample  system.conf
[root at echo etc]# modinfo dahdi
modinfo: could not open dahdi: Is a directory
[root at echo etc]# modinfo --version
module-init-tools version 3.3-pre2
                
> modinfo dahdi fails when run from /etc on centos 5
> --------------------------------------------------
>
>                 Key: DAHTOOL-65
>                 URL: https://issues.asterisk.org/jira/browse/DAHTOOL-65
>             Project: DAHDI-Tools
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>         Environment: Centos 5. Issue in modprobe seems to have been fixed in Centos 6.
>            Reporter: Tzafrir Cohen
>            Assignee: Russ Meyerriecks
>            Severity: Minor
>
> 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?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira