Dear all,
I have a working cgi script, well from the commandline.
I haven't enabled -T, but that will be next.
I am using $|++ and CGI::Carp to get things to stdout etc. and show me
errors.
All the script does is creates an ISO file, writes a log and burns the CD
with some Javascript quesions t
Are you sure that cdrecord needs to run as root? You might check into
changin permissions on the device itself. Or if this is a trusted
machine/environment (I assume it is, 'cause most people don't write web apps
to burn CDs), then you could suid cdrecord itself as root. Be sure you
understand
On Fri, 25 Feb 2005, Gavin Henry wrote:
> [...] the problem is [...] cdrecord needs to be run as root.
I assume cdrecord is being invoked from a system command, right?
Have you considered prefixing that command with `sudo`, and going into
the sudoers file to allow the www user that privilige?
> On Fri, 25 Feb 2005, Gavin Henry wrote:
>
>> [...] the problem is [...] cdrecord needs to be run as root.
>
> I assume cdrecord is being invoked from a system command, right?
I know have it running fine using -T and declaring ENN{PATH} as according
to the "Security" section of the camel.
Yeah,
Chris Devers wrote:
On Fri, 25 Feb 2005, Gavin Henry wrote:
[...] the problem is [...] cdrecord needs to be run as root.
I assume cdrecord is being invoked from a system command, right?
Have you considered prefixing that command with `sudo`, and going into
the sudoers file to allow the www user
--
Just getting into the best language ever...
Fancy a [EMAIL PROTECTED] Just ask!!!
> Chris Devers wrote:
>> On Fri, 25 Feb 2005, Gavin Henry wrote:
>>
>>
>>>[...] the problem is [...] cdrecord needs to be run as root.
>>
>>
>> I assume cdrecord is being invoked from a system command, right?
>
I will be out of the office starting 17.02.2005 and will not return until
28.02.2005.
I will respond to your message when I return.
+=+
This message may contain confidential and/or privileged
information. If you are not the addressee or au
Chris Devers <[EMAIL PROTECTED]> suggested:
> Have you considered prefixing that command with `sudo`, and
> going into the sudoers file to allow the www user that privilige?
>
> Of course, it would be a bit more complicated than that, as
> sudo will prompt for a password that you have to pass ba
