[*BSD-only] RFE: run-mozilla.sh should populate ${XPSERVERLIST} on *BSD-platforms if it was not set yet

RESOLVED INCOMPLETE

Status

--
enhancement
RESOLVED INCOMPLETE
16 years ago
9 years ago

People

(Reporter: roland.mainz, Assigned: roland.mainz)

Tracking

Trunk
x86
FreeBSD

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

16 years ago
[Followup to bug 178623 ("run-mozilla.sh should populate ${XPSERVERLIST} if it
was not set yet") - which only handled the issue for SYSV Unix, Solaris and
Linux which have /etc/init.d/]

RFE: "run-mozilla.sh" should populate ${XPSERVERLIST} if it was not set yet
(Assignee)

Updated

16 years ago
Summary: [*BSD-only] RFE: run-mozilla.sh should populate ${XPSERVERLIST} if it was not set yet → [*BSD-only] RFE: run-mozilla.sh should populate ${XPSERVERLIST} on *BSD-platforms if it was not set yet
(Assignee)

Comment 1

16 years ago
See bug 179911 ("RFE: run-mozilla.sh should populate ${XPSERVERLIST} on AIX if
it was not set yet") for the AIX-version of this RFE...
Product: Browser → Seamonkey

Comment 2

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 3

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

9 years ago
I don't see any useful stuff in this bug for SeaMonkey specifically. Please
file new bugs in the correct places if there are still issues.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.