I agree with Mike, although I'm always nervous of scripting things that run as root... What if I somehow put a problem in that ended up doing something as disastrous as "rm -fr /" as while I was root...<br>
<br>
Preferably, ditch perl altogether and look at sudo. This let's normal users run programs as root by supplying their own login password.<br>
<br>
Sudo has a configuration file that defines which users can run which programs. So, if a user's account became compromised you would not have a wide open system.<br>
<br>
You could then set up your perl script owned and executable by root only, and have access to it controlled by sudo. Another advantage of this would be that the program would only be available to users authorised by sudo, and not to eceryone who could access it.<br>
<br>
Can't remember the URL for sudo, but a search on your local SunSite should bring back plenty of hits.