Do you mean the:Blaster wrote:What's the deal with the ../../ in the path configs? Isthere a reason this is there?
Code: Select all
[path]
read-data=__PATH__executable__/../../data
write-data=__PATH__executable__/../..
Code: Select all
systemctl status -l factorioCode: Select all
Unit factorio.service entered failed state.
factorio.service failed.I've given you some suggestions in your github issue.TheEisbaer wrote:It's my first time using linux CentOS 7, and this message doesn't seem right, any advice?
You are most welcome, glad you find it usefulnevniv wrote:I just wanted to say thank you for making this script.
Ouch, I had not thought that one through, currently the user running the install script needs write permission in the directory where you want to install the "factorio" directory.Klynn wrote:I need permission to write to /opt in order to do the install, but I also believe I should not be running the install as root.
Yes, I do have a Factorio account. I am installing all of the Factorio stuff into /opt/ (isn't that where the install script does it automatically?) It seems to be a bad idea to chown the whole /opt/ directory away from root, right?nevniv wrote:I can try to explain with my intermediate linux knowledge and beer I have consumed tonight..hopefully I make sense
Did you make an extra user account for factorio yet? That would be best practice.
If you do a "ls -l" on the directory, you should see who owns the files you are trying to modify. You could do the install with any account, not a real big deal. But at the end when you actually want to run it, that's when I'd recommend you use the separate factorio account.
If the accounts are owned by your username, or root, you can do "chown -R username:username *" to give ownership of the directory you are in and all subdirectories to whatever factorio account you have created.
Then to run the init script you can do sudo -u (username here) service factorio (command). For example I do "sudo -u factorio service factorio start"
As long as your factorio account owns all the files for factorio and the init scripts, when you try to run it you should be good to go I think.
Okay, I installed to /opt/ as that seems to be the standard thing to do (and when you're piecing together instructions on the internet to run a program in a command line on an OS you're not super familiar with, it seems like deviating from the standard is asking for confusion).Bisa wrote:Ouch, I had not thought that one through, currently the user running the install script needs write permission in the directory where you want to install the "factorio" directory.Klynn wrote:I need permission to write to /opt in order to do the install, but I also believe I should not be running the install as root.
To get around this, you can either:
1. Install in a directory where the factorio user has write access (such as it's own home directory /home/factoriouser/factorio)
3. Grant the factorio user temporary write permissions in /opt (I do not endorse this approach but it is an option...)
2. Run as root (but yes, good call, do not blindly run things as root!)
Thank you for pointing this out, I'll see if I can make it more clear that the directory in which you want to install needs to be writable.
I don't do the whole directory, just the factorio-related folders. In my case it is /opt/factorio and /opt/factorio-init. I do not remember if I deviated from the norm at all when installing.Klynn wrote:Yes, I do have a Factorio account. I am installing all of the Factorio stuff into /opt/ (isn't that where the install script does it automatically?) It seems to be a bad idea to chown the whole /opt/ directory away from root, right?nevniv wrote:I can try to explain with my intermediate linux knowledge and beer I have consumed tonight..hopefully I make sense
Did you make an extra user account for factorio yet? That would be best practice.
If you do a "ls -l" on the directory, you should see who owns the files you are trying to modify. You could do the install with any account, not a real big deal. But at the end when you actually want to run it, that's when I'd recommend you use the separate factorio account.
If the accounts are owned by your username, or root, you can do "chown -R username:username *" to give ownership of the directory you are in and all subdirectories to whatever factorio account you have created.
Then to run the init script you can do sudo -u (username here) service factorio (command). For example I do "sudo -u factorio service factorio start"
As long as your factorio account owns all the files for factorio and the init scripts, when you try to run it you should be good to go I think.
Bisa or someone else may have to help you with that.Ah, I was worried about that dumping my save files. I ended up running the factorio-update script manually, followed by the Factorio --apply-update flag. I noticed when I ran that there was some feedback about downloading the update directly, which makes me wonder if the headless server actually has a built in auto updater?nevniv wrote:I don't do the whole directory, just the factorio-related folders. In my case it is /opt/factorio and /opt/factorio-init. I do not remember if I deviated from the norm at all when installing.Klynn wrote:Yes, I do have a Factorio account. I am installing all of the Factorio stuff into /opt/ (isn't that where the install script does it automatically?) It seems to be a bad idea to chown the whole /opt/ directory away from root, right?nevniv wrote:I can try to explain with my intermediate linux knowledge and beer I have consumed tonight..hopefully I make sense
Did you make an extra user account for factorio yet? That would be best practice.
If you do a "ls -l" on the directory, you should see who owns the files you are trying to modify. You could do the install with any account, not a real big deal. But at the end when you actually want to run it, that's when I'd recommend you use the separate factorio account.
If the accounts are owned by your username, or root, you can do "chown -R username:username *" to give ownership of the directory you are in and all subdirectories to whatever factorio account you have created.
Then to run the init script you can do sudo -u (username here) service factorio (command). For example I do "sudo -u factorio service factorio start"
As long as your factorio account owns all the files for factorio and the init scripts, when you try to run it you should be good to go I think.
I've never tried to get the auto-update to work, I just download manually.
I just download the headless version, SFTP it up, then tar -xvf it over the current one
You are welcome!tacgnol wrote:thanks in advance!
Hi, I'm sure you got it sorted eventually
