![]() SIGINT should be reserved for terminal interrupt, and applications should not otherwise send it to other processes but there's nothing stopping them doing so, so it's still also possible that something did a kill(postgres_pid, SIGINT) ( kill -s INT or kill -INT or kill -2 in a shell). I know earlier today I waited two hours to login in and then shortly after it crashed and no one else was able to get on. Its not like that program doesnt do a multitude of things to help server owners. Login Portal has been down most of the day. Yeah, screw me for trying to help people, hey. Be sure to have your IP static and port forward 5121 UDP. That's the signal that is sent to the foreground process group of a terminal when you press Ctrl-C in that terminal. For anyone looking for a SIMPLE a TRUSTFULL way to start a server, just go to steamappscommonNeverwinter Nightsbinwin32 and run as admin 'nwserver.exe'. On most systems, signal 2 will be SIGINT. You can tell what signal that was by running: $ kill -l 130 ![]() So here, most likely, the process died of a signal 2. Echo of Soul General Discussions :: Steam Community. However, because so many shells follow that convention of having 128 + signal_number, programs know to avoid using those values above 128 for their exit code (or when they do exit(130), it's to report the death of a child that dies of a signal 2 like some shells do under some circumstances). So if you get a number of 130, there's an ambiguity in that you don't know whether the process dies of a signal 2 or just did an exit(130).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |