OnDemand User Group
Support Forums => Other => Topic started by: jsquizz on November 06, 2017, 07:05:16 AM
-
Heres a weird one, couldnt figure out a better spot to put it..
All my application groups use a custom exit. Not sure what it does, not a C dev, and I dont think theres any left sadly here.
We run a basic ARSLOAD daemon as root..when a file comes in it loads, the exit is called, and everything loads fine.
When I try issuing arsload -nvf -g appgroup filename <--I get an 88 record indicating the exit couldnt execute. The same thing happens with sudo.
Any thoughts on this? Does my question make sense?
-
If you've upgraded, the exit needs to be recompiled for the new version of CMOD.
Otherwise, check permissions on the file itself... Is it executible, etc.
-JD.
-
Yeah, perms are good. They are actually 777.
No upgrades..We are on 8.5 and when the daemon loads files it runs with NP..just when I execute manually, so its a pain to load files when testing.
-
Heh. 777 is bad. 555 is the way to go. (You generally don't want everyone being able to write to executibles -- they can replace your 'good' code with 'bad' code and run with your authority/permissions.)
As for the issues running interactively... Maybe you're missing some environment variables, or it's not in your path?
-JD.
-
That's what I am thinking. Something with the path, an ldd showed some dependencies..
thanks for the tip on 555, it's always been like that i believe...
>:( :o