… | |
… | |
780 | </dd> |
780 | </dd> |
781 | <p></p> |
781 | <p></p> |
782 | <dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br /> |
782 | <dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br /> |
783 | </dt> |
783 | </dt> |
784 | <dd> |
784 | <dd> |
785 | Despite it's name, rxvtd is not a real daemon, but more like a |
785 | Try <code>rxvtd -f -o</code>, which tells rxvtd to open the |
786 | server that answers rxvtc's requests, so it doesn't background |
786 | display, create the listening socket and then fork. |
787 | itself. |
|
|
788 | </dd> |
|
|
789 | <dd> |
|
|
790 | <p>To ensure rxvtd is listening on it's socket, you can use the |
|
|
791 | following method to wait for the startup message before continuing:</p> |
|
|
792 | </dd> |
|
|
793 | <dd> |
|
|
794 | <pre> |
|
|
795 | { rxvtd & } | read</pre> |
|
|
796 | </dd> |
787 | </dd> |
797 | <p></p> |
788 | <p></p> |
798 | <dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br /> |
789 | <dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br /> |
799 | </dt> |
790 | </dt> |
800 | <dd> |
791 | <dd> |