Thx for the tips from Long Xiang and Xu, I've found the solution now: If you want to support debugging multiple instances of xwalk launched by multiple users in same time. You can create "xwalk.service" in the path "~/.config/systemd/usr/". That file will overwhelm "/usr/lib/systemd/user/xwalk.service ". Then you can assign different port for different users.
---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Jun 2014 03:46:31 +0000 From: "Wang, Peter H" <[email protected]> To: "[email protected]" <[email protected]> Subject: [Crosswalk-dev] Questions about multi-user and command line option "remote-debugging-port" for tizen xwalk Message-ID: <8453782e7578064a91f1bdf59ad4625cd8b...@shsmsx102.ccr.corp.intel.com> Content-Type: text/plain; charset="us-ascii" Hi all, I'm investigating the bug [XWALK-1858<https://crosswalk-project.org/jira/browse/XWALK-1858>] and have questions of the original design, so ask the help here. The root reason of this bug is pretty straightforward: For multiple users, Tizen IVI allows to launch multiple instances of xwalk, but there is only one place (/usr/lib/systemd/user/xwalk.service) to assign devtools socket port for all instances, so they're competing to listen same socket port. My questions are: (1) Should we allow to launch multiple instances of xwalk for multiple users? (2) Can we add a new command option like "set-remote-debugging-port" for "xwalkctl" to give each instance of xwalk a chance to choose their own port? I believe we've removed the "remote-debugging-port" for "xwalkctl" because if each APP have a chance to choose port will cause chaotic, since they are supposed to share common port of "xwalk". Watiting for your comments. Thank you very much. Peter Wang _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
