Added command to path won't execute












1















Okay so i tried to install NBFC.
I added the command to the $PATH permanently.
But if i say nbfc the shell doesn't know it.
I use the bash shell.
I added in the .bashrc file following



export PATH=$PATH:/opt/nbfc/


According to that official Installation page of NBFC its correct.
Check it here: https://github.com/hirschmann/nbfc/wiki/First-steps



The files in the /opt/nbfc/ directory are following:




clipr.dll NLog.dll

Configs Plugins

ec-probe.exe StagWare.BiosInfo.dll

nbfc.exe StagWare.FanControl.Configurations.dll

nbfc.exe.config StagWare.FanControl.dll

NbfcService.exe StagWare.FanControl.Service.dll

NbfcService.exe.config StagWare.Settings.dll

nbfcservice.sh System.IO.Abstractions.dll




Im new to Linux. Hope you can help out.



Okay it works but i have to call it with:



mono /opt/nbfc/nbfc.exe









share|improve this question

























  • Did you restart the shell? Did you try hash -r?

    – DavidPostill
    Dec 30 '18 at 20:02











  • Did you go out and back in again? Also, is mini installed?

    – davidgo
    Dec 30 '18 at 20:03











  • @DavidPostill yup its definitly in the $PATH variable

    – Stefan xyz
    Dec 30 '18 at 20:50











  • @davidgo what do you mean?

    – Stefan xyz
    Dec 30 '18 at 20:50











  • Sorry to ask a dumb question, but did you by chance install a Windows package instead of one for Linux? The .DLL and .EXE files made me wonder. At any rate, it looks like the executable's name is "nbfc.exe" not merely "nbfc". What happens if you try to invoke the name "nbfc.exe"?

    – Jim L.
    Jan 3 at 0:56


















1















Okay so i tried to install NBFC.
I added the command to the $PATH permanently.
But if i say nbfc the shell doesn't know it.
I use the bash shell.
I added in the .bashrc file following



export PATH=$PATH:/opt/nbfc/


According to that official Installation page of NBFC its correct.
Check it here: https://github.com/hirschmann/nbfc/wiki/First-steps



The files in the /opt/nbfc/ directory are following:




clipr.dll NLog.dll

Configs Plugins

ec-probe.exe StagWare.BiosInfo.dll

nbfc.exe StagWare.FanControl.Configurations.dll

nbfc.exe.config StagWare.FanControl.dll

NbfcService.exe StagWare.FanControl.Service.dll

NbfcService.exe.config StagWare.Settings.dll

nbfcservice.sh System.IO.Abstractions.dll




Im new to Linux. Hope you can help out.



Okay it works but i have to call it with:



mono /opt/nbfc/nbfc.exe









share|improve this question

























  • Did you restart the shell? Did you try hash -r?

    – DavidPostill
    Dec 30 '18 at 20:02











  • Did you go out and back in again? Also, is mini installed?

    – davidgo
    Dec 30 '18 at 20:03











  • @DavidPostill yup its definitly in the $PATH variable

    – Stefan xyz
    Dec 30 '18 at 20:50











  • @davidgo what do you mean?

    – Stefan xyz
    Dec 30 '18 at 20:50











  • Sorry to ask a dumb question, but did you by chance install a Windows package instead of one for Linux? The .DLL and .EXE files made me wonder. At any rate, it looks like the executable's name is "nbfc.exe" not merely "nbfc". What happens if you try to invoke the name "nbfc.exe"?

    – Jim L.
    Jan 3 at 0:56
















1












1








1








Okay so i tried to install NBFC.
I added the command to the $PATH permanently.
But if i say nbfc the shell doesn't know it.
I use the bash shell.
I added in the .bashrc file following



export PATH=$PATH:/opt/nbfc/


According to that official Installation page of NBFC its correct.
Check it here: https://github.com/hirschmann/nbfc/wiki/First-steps



The files in the /opt/nbfc/ directory are following:




clipr.dll NLog.dll

Configs Plugins

ec-probe.exe StagWare.BiosInfo.dll

nbfc.exe StagWare.FanControl.Configurations.dll

nbfc.exe.config StagWare.FanControl.dll

NbfcService.exe StagWare.FanControl.Service.dll

NbfcService.exe.config StagWare.Settings.dll

nbfcservice.sh System.IO.Abstractions.dll




Im new to Linux. Hope you can help out.



Okay it works but i have to call it with:



mono /opt/nbfc/nbfc.exe









share|improve this question
















Okay so i tried to install NBFC.
I added the command to the $PATH permanently.
But if i say nbfc the shell doesn't know it.
I use the bash shell.
I added in the .bashrc file following



export PATH=$PATH:/opt/nbfc/


According to that official Installation page of NBFC its correct.
Check it here: https://github.com/hirschmann/nbfc/wiki/First-steps



The files in the /opt/nbfc/ directory are following:




clipr.dll NLog.dll

Configs Plugins

ec-probe.exe StagWare.BiosInfo.dll

nbfc.exe StagWare.FanControl.Configurations.dll

nbfc.exe.config StagWare.FanControl.dll

NbfcService.exe StagWare.FanControl.Service.dll

NbfcService.exe.config StagWare.Settings.dll

nbfcservice.sh System.IO.Abstractions.dll




Im new to Linux. Hope you can help out.



Okay it works but i have to call it with:



mono /opt/nbfc/nbfc.exe






linux bash shell linux-mint






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 3 at 10:40







Stefan xyz

















asked Dec 30 '18 at 19:40









Stefan xyzStefan xyz

42




42













  • Did you restart the shell? Did you try hash -r?

    – DavidPostill
    Dec 30 '18 at 20:02











  • Did you go out and back in again? Also, is mini installed?

    – davidgo
    Dec 30 '18 at 20:03











  • @DavidPostill yup its definitly in the $PATH variable

    – Stefan xyz
    Dec 30 '18 at 20:50











  • @davidgo what do you mean?

    – Stefan xyz
    Dec 30 '18 at 20:50











  • Sorry to ask a dumb question, but did you by chance install a Windows package instead of one for Linux? The .DLL and .EXE files made me wonder. At any rate, it looks like the executable's name is "nbfc.exe" not merely "nbfc". What happens if you try to invoke the name "nbfc.exe"?

    – Jim L.
    Jan 3 at 0:56





















  • Did you restart the shell? Did you try hash -r?

    – DavidPostill
    Dec 30 '18 at 20:02











  • Did you go out and back in again? Also, is mini installed?

    – davidgo
    Dec 30 '18 at 20:03











  • @DavidPostill yup its definitly in the $PATH variable

    – Stefan xyz
    Dec 30 '18 at 20:50











  • @davidgo what do you mean?

    – Stefan xyz
    Dec 30 '18 at 20:50











  • Sorry to ask a dumb question, but did you by chance install a Windows package instead of one for Linux? The .DLL and .EXE files made me wonder. At any rate, it looks like the executable's name is "nbfc.exe" not merely "nbfc". What happens if you try to invoke the name "nbfc.exe"?

    – Jim L.
    Jan 3 at 0:56



















Did you restart the shell? Did you try hash -r?

– DavidPostill
Dec 30 '18 at 20:02





Did you restart the shell? Did you try hash -r?

– DavidPostill
Dec 30 '18 at 20:02













Did you go out and back in again? Also, is mini installed?

– davidgo
Dec 30 '18 at 20:03





Did you go out and back in again? Also, is mini installed?

– davidgo
Dec 30 '18 at 20:03













@DavidPostill yup its definitly in the $PATH variable

– Stefan xyz
Dec 30 '18 at 20:50





@DavidPostill yup its definitly in the $PATH variable

– Stefan xyz
Dec 30 '18 at 20:50













@davidgo what do you mean?

– Stefan xyz
Dec 30 '18 at 20:50





@davidgo what do you mean?

– Stefan xyz
Dec 30 '18 at 20:50













Sorry to ask a dumb question, but did you by chance install a Windows package instead of one for Linux? The .DLL and .EXE files made me wonder. At any rate, it looks like the executable's name is "nbfc.exe" not merely "nbfc". What happens if you try to invoke the name "nbfc.exe"?

– Jim L.
Jan 3 at 0:56







Sorry to ask a dumb question, but did you by chance install a Windows package instead of one for Linux? The .DLL and .EXE files made me wonder. At any rate, it looks like the executable's name is "nbfc.exe" not merely "nbfc". What happens if you try to invoke the name "nbfc.exe"?

– Jim L.
Jan 3 at 0:56












0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389057%2fadded-command-to-path-wont-execute%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389057%2fadded-command-to-path-wont-execute%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Terni

A new problem with tex4ht and tikz

Sun Ra