|
Title: Server-to-Server Communications Systems Post by: N3hpy50X3 on April 22, 2013, 08:20:05 PM (http://s21.postimg.org/dnt159d93/Screenshot_from_2013_04_23_10_17_04.png)
NET SEND <server> <msg> NET SEND * <msg> sends a message to all Group Servers and ping should leave logs on the server you ping unless you have a higher level...or just make ping do all the dirty work and let us ping message logs :16: this would mean having a Dedicated Notifications Server allowing us to notify each other without needing to crack their server (and possibly incase of an emergency where they won't allow us to crack it to leave log messages) ...it would have to be dedicated since our IP would be included in the message logged <server IP>: "message" maybe we can have a new Messenger software that runs a process on both servers inorder for an communications link to become established (no denying/undoubtedly it has been read after the process has been killed) (http://s22.postimg.org/h4i85r61s/Screenshot_from_2013_04_23_11_10_00.jpg) Title: Re: Server-to-Server Communications Systems Post by: Exousia on April 23, 2013, 01:34:27 AM So, you wanna open everyone up to having their logs spammed?
Title: Re: Server-to-Server Communications Systems Post by: N3hpy50X3 on April 23, 2013, 03:13:43 PM say after the message is logged it can open up a process with a 1m timer on it and you can't log any further messages until you complete the unkillable process or they reply (and thereby killing the process for you automatically)...you can only kill it after the timer runs and it becomes task complete
|