Very Computer

Are their any types of permission differences from running a program from
rc2.d as compared to running a program from the command line (while logged
in as root)?

I am having a cu /dev/modem "/var/lock/tmpfile" access problem when my
program runs during startup (from the rc2.d).  

If I kill the program and run it manually when logged in as root, the cu
access problems disappear.

Does anybody have a clue to as what is going on?

Thanks,
Mike Samson

------------------  Posted via CNET Linux Help  ------------------
                    http://www.searchlinux.com

Quote:> I am having a cu /dev/modem "/var/lock/tmpfile" access problem when my
> program runs during startup (from the rc2.d).

A  problem that appears occasionally , is the lack of PATH with
chron jobs,  so maybe something is lacking in the env during the
boot that cu needs ?

Hope you fix it soon,
Cheers,
Steve Houseman

--

currently  steve.houseman at * net

        There could be resource limits in force later. Now a program could,
theoretically, change its resource limits (since it has root
permissions) but most programs don't do so.

        This most commonly happens when someone su's to root and then runs
Apache. Whoops, Apache now has the same process limit the user who su'd
has.

        It's inelegant, but I usually remove all resource limits from users who
are likely to su.

        DS