OK, so yes, it runs. This means that /sbin/e-smith isn't in your path. Time for some troubleshooting questions:
- Are you logged in as the root user? If not, there's your problem--you need to be root to use signal-event
- If you are root, how did you log in as root? Did you log in directly as root, or did you log in as another user and then use su?
- If you used su, what exact syntax did you use? Did you just type "su", did you use "su -", or something else?
What I suspect is that you logged in as another user, used su to get root privileges, and did not do "su -".
When you log in as a user (let's call the user "fred"), the system loads fred's environment files--.bash_profile, .bashrc, etc. These set a number of things for fred, like the arrangement of the shell prompt, command aliases, and the PATH variable. The PATH variable defines where the system will look to run any command you enter in the shell, and the standard user's PATH does not include /sbin/e-smith (which is where the signal-event command is located).
When you run su, you are switched to the user specified (or root if no user is specified), but that user's environment files aren't read. So you're now the root user, but root's PATH and such aren't applied--you're still using fred's path, prompt, aliases, etc. So, /sbin/e-smith still isn't in your path. To correct this, use "su -" instead of "su".
10 Replies
3037 Views