On Mon, 05 Aug 2013 21:13:49 -0500
Zack Middleton wrote:
> On 08/05/2013 08:51 PM, YuGiOhJCJ Mailing-List wrote:
> > On Mon, 05 Aug 2013 12:48:43 +0100
> > Tim Angus wrote:
> >
> >> On 05/08/13 12:18, YuGiOhJCJ Mailing-List wrote:
> >>> We can see that the program wants to write into the "/root"
On 08/05/2013 08:51 PM, YuGiOhJCJ Mailing-List wrote:
On Mon, 05 Aug 2013 12:48:43 +0100
Tim Angus wrote:
On 05/08/13 12:18, YuGiOhJCJ Mailing-List wrote:
We can see that the program wants to write into the "/root" directory.
The "ioq3" user has not the permission to write to this directory.
On Mon, 05 Aug 2013 12:48:43 +0100
Tim Angus wrote:
> On 05/08/13 12:18, YuGiOhJCJ Mailing-List wrote:
> > We can see that the program wants to write into the "/root" directory.
> > The "ioq3" user has not the permission to write to this directory.
> > What is the best strategy to correct this be
On 05/08/2013 13:18, YuGiOhJCJ Mailing-List wrote:
> When I am running the ioquake3 1.36 server on linux at booting, I don't want
> to run it as the "root" user because it is not safe.
> I prefer to use an "ioq3" user dedicated to this task.
> This is what happened when I run the server as the "io
On 05/08/13 12:18, YuGiOhJCJ Mailing-List wrote:
We can see that the program wants to write into the "/root" directory.
The "ioq3" user has not the permission to write to this directory.
What is the best strategy to correct this behavior ?
Put +set com_homepath /somewhere/you/can/write on the c
Hello,
When I am running the ioquake3 1.36 server on linux at booting, I don't want to
run it as the "root" user because it is not safe.
I prefer to use an "ioq3" user dedicated to this task.
This is what happened when I run the server as the "ioq3" user using sudo as
"root":
# sudo -u ioq3 /usr
