@mfalkvidd
Thank You for the answer.
@mfalkvidd said in mysgw: bind: Address already in use:
As mentioned in the troubleshooting section, look in /var/log/syslog to see the gateway output of the existing instance. Don't start a new one.
Ohh... Thats a lot more clear now... I thought command "sudo ./bin/mysgw -d" is not a service start, but just something like output mirror. Like "tail". Could I somehow use tail for watching real time output on ./bin/mysgw -d ?
Also, it seems your sudo key has gotten stuck :( If you missed that not every command is preceeded by sudo in the build instructions, maybe it is worth considering that you missed something else?
Sorry for dumb questions, but how I make that sudo key stuck? It's becose of that I start a few mysgw services?
Another silly question, becose I'm very "advanced user" in UNIX, my best friend is called desktop there, and I know basically just install, nano, cp, rm commands, I need to ask :) Is there should be difference if I will use "make" instead of "sudo make". Sudo means that I run this command by root user, but does it make difference between "make" or "sudo make"? And if I remember clearly if I run only "make" - raspberry pi starts to swearing, but with sudo, it's ok.
When I install the gateway by command "sudo make install" I can see that installing was successful, there is info that if I want to run this on boot I need to run two lines:
sudo systemctl enable mysgw.service
sudo systemctl start mysgw.service
But now, I guess, I do not need them both, because start on boot is described in "sudo make install"?
