Closed Bug 134909 Opened 18 years ago Closed 3 years ago

RFE: A way to shutdown Mozilla from the command line (x-remote or signal).

Categories

(Core Graveyard :: X-remote, enhancement)

x86
Linux
enhancement
Not set

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: mozilla-bugs, Assigned: blizzard)

References

Details

(Keywords: helpwanted)

Attachments

(2 obsolete files)

Quite often I find miself wishing for a way to shut down Mozilla from the
command line. Sometimes I want to quit it on some remote machine. Sometimes the
Mozilla UI gets to a state when it's hard or impossible to get to the Ctrl-Q,
but the back-end is still there.

Currently, I just end up killing Mozilla, but then it (AFAIK) does not get a
chance to write out all the configs, close the dbs, etc. It would be nice to have a 
mozilla -remote "Quit()" 
option.
Doesn't do a 'killall mozilla-bin' exactly that? The signal should allow mozilla
to finish gracefully as opposed to 'killall -9 mozilla-bin'.
AFAIK, if you have managed to hang Mozilla, an xremote quit capability will not
help.
*** Bug 191851 has been marked as a duplicate of this bug. ***
OK, this is a first attempt - I do not know a lot about the Mozilla C++ code so
I am probably missing something important here, but it works insofar as the
command indeed closes (or crashes? :) ) the application.

The idea is that the command is "closeall()" or "closeall(somearg)" to request
a confirmation prompt if more than one tab is open.
Keywords: helpwanted
Attached patch Minor corrections (obsolete) — Splinter Review
Attachment #138432 - Attachment is obsolete: true
Attachment #138451 - Attachment is obsolete: true
(In reply to comment #2)
> see also bug 132641

So -kill won't close the DBs and do what this bug is requesting?

I'd be interested in something that causes mozilla/TB/FF to shutdown gracefully
upon a SIGTERM signal.
Depends on: 132641
*** Bug 345601 has been marked as a duplicate of this bug. ***
Hi,

I just want to know if there is any plan to implement a handler for SIGTERM, which is rather common on POSIX platform.
Right now, sending SIGTERM shuts down the process in an unclean way, but most of users expect to have a clean exit with this signal, not as the SIGKILL signal.
See Also: → 288127
Mass resolving a bunch of old bugs in the x-remote component in preparation for archiving it. If this bug is still valid and useful, please move it to the "Toolkit: Startup and Profile System" component and reopen it.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.