Legal Opinion

Longstaff v. Hurd

Supreme Court of Connecticut

Decided June 22, 1895PublishedCited by 5 opinions

Application for the appointment of a receiver for a co-partnership, brought before the 'Son. F. B. Soil, a judge of the Superior Court, in Fairfield County, upon whose order a receiver was appointed.

Read the full summary

Application for the appointment of a receiver for a co-partnership, brought before the 'Son. F. B. Soil, a judge of the Superior Court, in Fairfield County, upon whose order a receiver was appointed. Subsequently certain attaching creditors of the partnership filed intervening applications, praying to be made parties to the action, and alleging that the appointment of the receiver was illegal, or, if of any validity, that the receiver’s title to the property attached ought to be postponed, or held subordinate, to the title claimed to have been acquired by the respective attaching creditors.…

1Opinion of the CourtTobbahce, J.

On the 16th of August, 1894, George W. Longstaff of Bridgeport in this State, presented his application to one of the judges of the Superior Court, under the statute, alleging that he and Frank W. Hurd also of Bridgeport, were formerly partners in business in the county of Fairfield; that the partnership had been dissolved; that the partners could not agree upon the disposition of the partnership effects and the settlement of its affairs; and asking said judge to forthwith appoint a receiver to take charge of the partnership property and to dispose of, manage and apply the same, as the…

2Cases cited1 opinion

  1. New Haven Wire Co. CasesSupreme Court of Connecticut · 1888

3Cited by5 opinions

  1. Siegemund v. Building CommissionerMassachusetts Supreme Judicial Court · 1928
  2. American Bank Trust Co. v. Feeney Tool Co., Inc.Supreme Court of Connecticut · 1927
  3. Ratick v. ScaloSupreme Court of Connecticut · 1974
  4. Stratton v. WardConnecticut Superior Court · 1983
  5. Hammer v. IsraelNew Jersey Court of Chancery · 1919

Showing a preview — retrieve the full document via the Exa API.

Powered by the Exa API