Closed xero-lib closed 8 months ago
Pushed to master since dev appeared stagnant.
I have a feeling the right way to fix this may just be to set the permissions to 666
when we create the socket file, so that this isn't an issue at all.
We should probably also allow a config option to override the permissions incase people don't want other users on the system to access the socket, in which case some improved error messaging is still helpful.
Do you want to try tackle that as well?
I have a feeling the right way to fix this may just be to set the permissions to
666
when we create the socket file, so that this isn't an issue at all.We should probably also allow a config option to override the permissions incase people don't want other users on the system to access the socket, in which case some improved error messaging is still helpful.
Do you want to try tackle that as well?
Seems unnecessary, but if that's how you'd rather do it, I could give it a go.
It appears that setting those permissions won't even work anyway. Asking users to remove the file manually will have to do.
It appears that setting those permissions won't even work anyway. Asking users to remove the file manually will have to do.
Yeah, I was fiddling with it and couldn't get it to work properly. I think this is currently the best solution.
Solution to #112, where wired would panic without proper explanation after attempting to remove the existing socket with missing permissions.