| commit | 0b624b4ceee63ce45135cdbb80f2807c20b48646 | |
| author | Stephen Boyd <bebarino@gmail.com> | |
| Mon, 23 Nov 2009 07:09:12 +0000 (22 23:09 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 24 Nov 2009 05:31:01 +0000 (23 21:31 -0800) | ||
| tree | cd99912c9845ed8953f61fa358f12b89488cb882 | treesnapshot (tar.gz zip) |
| parent | 1ddf5efc66d92282e3c654ebf263538a0df2ac24 | commitdiff |
instaweb: restart server if already running
Running 'git instaweb' when an instaweb server is already running will
fail (at least when the port is the same) and overwrite the pid file
used to track the currently running server. This turns out to be
especially annoying when the user tries to stop the previously running
server with 'git instaweb --stop' and is instead greeted with an error
message because the pid file has been destroyed.
Instead of allowing a user to start two instaweb servers, stop the
currently running server first and then start the new one. This should
be fine because it was never really possible to start two instaweb
servers in the first place due to the pid file issue outlined above.
Signed-off-by: Stephen Boyd <bebarino@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Running 'git instaweb' when an instaweb server is already running will
fail (at least when the port is the same) and overwrite the pid file
used to track the currently running server. This turns out to be
especially annoying when the user tries to stop the previously running
server with 'git instaweb --stop' and is instead greeted with an error
message because the pid file has been destroyed.
Instead of allowing a user to start two instaweb servers, stop the
currently running server first and then start the new one. This should
be fine because it was never really possible to start two instaweb
servers in the first place due to the pid file issue outlined above.
Signed-off-by: Stephen Boyd <bebarino@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| git-instaweb.sh | diffblobblamehistory |