A few small nits

[dgryski]

I've only quickly glanced over the code but I've noticed a few things:

• there are a few places you call log.Printf and then os.Exit. You can just call log.Fatalf instead, which does the same thing.
• instead of calling r.ReadString('\n'), use a bufio.Scanner: https://golang.org/pkg/bufio/#Scanner , it's a nicer API.
• remember that a reader can return io.EOF and data that was partially read. In the case of ReadString, you're assured that err != nil iff the data doesn't end in the delimiter, which in your case means likely an incomplete line was read, but it's still good to document that you're discarding a potentially incomplete line.
• your case in parseEvent returns an empty string for the error when the broadcast packet doesn't have two fields
• the cases for 'F', 'U', and 'P' can be combined: case "F", "U", "P": ...
• you're calling recover() directly. In order to catch a panic, recover() needs to be in a defer and you need to check the return value from recover to see if you're actually panicking or not.
• you're trying to trap os.Kill, which is SIGKILL, which you can't catch. You probably meant SIGTERM (but there's no constant for that in the os package, just pull syscall.SIGTERM directly.
• I'm not sure of the performance requirements here, but there's a lot of copying []byte -> string -> []byte. It's probably worth profiling to see if you can do away with the extra string conversion which will involve both a memory allocation and a data copy.

[sahildua2305]

Thanks a lot for reviewing and listing improvements @dgryski ❤️

I'll get to fixing/improving the things you mentioned one at a time soon.

EDIT: I took the liberty to modify the issue description into a checklist so that I can easily keep track of things to fix.