Can only run VIC as ./

[Des_Murray]

Hi,

I can't run vic except as  ./

flame2022_2, centos 7.6

In a terminal I type: vic -a -f

I get an error:  bash: vic: command not found...

I can however navigate to

cd /opt/Autodesk/io/bin/

then type  ./vic -a -f

I'm certain I didnt need to do all this navagating and dotslashing on my old machine. How can I have linux just run vic from the terminal?

tia

Des

[Des_Murray]

Hi,

I can't run vic except as  ./

flame2022_2, centos 7.6

In a terminal I type: vic -a -f

I get an error:  bash: vic: command not found...

I can however navigate to

cd /opt/Autodesk/io/bin/

then type  ./vic -a -f

I'm certain I didnt need to do all this navagating and dotslashing on my old machine. How can I have linux just run vic from the terminal?

tia

Des

[yann.laforest]

Hi Des,

Does the following command work on your end?

/opt/Autodesk/io/bin/vic -a

If not, what error message do you get after running the command?

Best,

Yann

[yann.laforest]

Hi Des,

Does the following command work on your end?

/opt/Autodesk/io/bin/vic -a

If not, what error message do you get after running the command?

Best,

Yann

[Beau_James]

Sounds like your aliases might be off for that OS user. 

Without jumping into the system to diagnose, you can make an alias:

alias newvic="/opt/Autodesk/io/bin/vic -a"

Run vic as you remember from the cli:

newvic

[Beau_James]

Sounds like your aliases might be off for that OS user. 

Without jumping into the system to diagnose, you can make an alias:

alias newvic="/opt/Autodesk/io/bin/vic -a"

Run vic as you remember from the cli:

newvic

[Des_Murray]

Hi Yann,

vic runs fine using

/opt/Autodesk/io/bin/vic -a

no errors. I'm ok with this, but for 5 years I swear I just used to type vic! What's different on this machine? 🙂

Des

[Des_Murray]

Hi Yann,

vic runs fine using

/opt/Autodesk/io/bin/vic -a

no errors. I'm ok with this, but for 5 years I swear I just used to type vic! What's different on this machine? 🙂

Des

[slabrie · Accepted solution]

Hello Des!

I guess your previous box was running Flame 2021.x and not 2022.  Since the 2022 release, we got rid of the application based user account, which had all the right paths defined for the various command line tools.

For now use the full path to run vic and we will have a look at your issue.

[slabrie · Accepted solution]

Hello Des!

I guess your previous box was running Flame 2021.x and not 2022.  Since the 2022 release, we got rid of the application based user account, which had all the right paths defined for the various command line tools.

For now use the full path to run vic and we will have a look at your issue.

[Des_Murray]

Hi,
this works. So can I use:

alias vic="/opt/Autodesk/io/bin/vic"

then type vic -a -f (or whatever switches I need) ?

thanks
D

[Des_Murray]

Hi,
this works. So can I use:

alias vic="/opt/Autodesk/io/bin/vic"

then type vic -a -f (or whatever switches I need) ?

thanks
D

[Des_Murray]

this makes sense, thanks 🙂
Des

[Des_Murray]

this makes sense, thanks 🙂
Des