At 12:20 13/07/99 -0400, you wrote:
>On Tue, 13 Jul 1999, you wrote:
>
>> For a program to run as root and not when su - root, it would have to
>> step thru parent pid's looking specificly for su (it could test the parent
>> pids uid, they all eventualy lead to root), which is posible but ugly.
>> As for editing system files, I am quite certain the filesystem drivers do
>> not check for su as a parent pid, so when editing files if your root or su
>> - root it will write the file. So if you do find a program that does this
>> let me know i'd like a look at it.
>>
>Ok....one I can give you right off the top is "timed" It
>will NOT run as SuperUser, but it WILL run as "root." It
>comes back with "timed command not found." This is from a
>text-mode prompt, not a window prompt, just a standard
>shell prompt. However, I run that logged in as "root" and
>it works just fine.
When you do "su" you don't always get the PATH environment of root
(depending on the system)
The above error was because "timed" is not in your path - not
because you cannot run it. Try "/usr/sbin/timed" instead.
ttfn
nick@nexnix
>
> --
> John Aldrich
> COL Tech Support
>=======================================
>Chattanooga Online Internet
> 423-267-8867
>
>
