"R. Quenett" wrote: > from Dave Anselmi: > > " run, rather than run an interactive shell. I don't know how to script > " the password to su (I'm sure there are several tricks you could use, > " but su isn't likely to make it easy). > > I surely hope not.<g> It seems like it would be a dangerous thing to > do but I was, through inattention, leaving a machine connected to the > net as root and I thought that was likely worse.
<snip> > These comments make sense to me, and I thank you for them. I'd still > have the original problem, tho, which is that I don't want to be root > when I run the script. Kurt Wall's suggestion of sudo looks as if it > might be just what the MD mandated. > > In the short term, I was able to get the script to run by increasing > some privileges here and there but I'm not comfortable with this in > the long term since I don't really understand very well what I did or > all the implications of it. Is your script a "connect to the 'net" script? You might describe what it does a little more - maybe your problem is already solved by someone more experienced than me (ppp dial-up for example). I don't recall a no password option to sudo, though there might be one. But of course you have to lock down what it can do in that case (e.g. don't give permission to run a script to someone who can edit the script). Dave _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
