Reputation: 276
I have a binary that listens using UDP waiting for commands. When started by the root user it works great. But if started by start-stop-daemon at boot up I see "Bad file descriptor" errors in the UDP routine.
This is a Linux/Ubuntu ARM based board running a 3.4.0-1489-omap4 kernel.
start-stop-daemon --version start-stop-daemon 1.16.1.2 for Debian
The start-stop-daemon command looks like this: start-stop-daemon --start --startas $home/program --pidfile $home/program.pid --make-pidfile --background -- -argument
Any ideas would be appreciated.
Upvotes: 0
Views: 253
Reputation: 276
Turns out that I was trying to connect before the network was up when I started from boot up scripts. I added a 10 second delay inside the application and the UDP communications started working. I'll have to revisit this when I have more time to create a proper solution.
Upvotes: 0