Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w7xGu-0004NO-0o for pgsql-general@arkaria.postgresql.org; Wed, 01 Apr 2026 15:14:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w7xGr-000wWw-2z for pgsql-general@arkaria.postgresql.org; Wed, 01 Apr 2026 15:14:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w7xGr-000wWo-0B for pgsql-general@lists.postgresql.org; Wed, 01 Apr 2026 15:14:18 +0000 Received: from fout-a2-smtp.messagingengine.com ([103.168.172.145]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w7xGn-0000000027H-2ewn for pgsql-general@lists.postgresql.org; Wed, 01 Apr 2026 15:14:17 +0000 Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfout.phl.internal (Postfix) with ESMTP id F23FBEC0266; Wed, 1 Apr 2026 11:14:11 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Wed, 01 Apr 2026 11:14:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1775056451; x=1775142851; bh=S08xzk0mwTvbIVXWAbKUhkqETdI5Y1NnXFEx05VORjE=; b= Xu38dTj77RnPLl6J5YZFbAKkUjfva64Z6NehO13CTL8vxByktDdTBu2Uzqv+mGWk ck/KlzSPIFzjPI80YpqubdVRXbC/aIwiIjitC3RP3Dengci+nJ/58Am7qEKF4SFT OJ+kG4xT17IdvB873R36se9xKJizd6dYwN/YmmiVODGzFBXmyHdy0wcDFs+5P8wY uYKwC34+CE3wLyCIdrkTi91FHirs0OlXKE+puBw+Jkr8dHy9lz8CSVKQwvvMj//7 LVZTcG1B6CAeZnYaafLs0zdwHEqtGmgAqtx6+VeKO36IgRnkl4qo8Yj+EOg6nJK7 a6iYWnDKM9IR6UWqr4Rscg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1775056451; x= 1775142851; bh=S08xzk0mwTvbIVXWAbKUhkqETdI5Y1NnXFEx05VORjE=; b=C HJoWFnf6uymCQx/3GWzutP7kbahPyKzNhCjLxOzvzXb0a1SHnCcvk1b6LYiIgqGI TVqSktRWbAY5leQjqS6pYKiYN0qMzC0ELpmZ7Rh/xgyfXyYrErCXoitPH68f9Pgj FQVGn7EqNB2Xpiza7mgHn5vj1vjGTbcQ3JLbPWf6VfgYUOnGBfWPuNgPN91A9Mgi vJrzqWpuYhj/QfK5Kjc5a8PuqmkI24oEKRn10pXCxB4VZyKi/iH/jWjxj1b9pQ8W 1E9lRqA7dGAXVzCv2kkn81/AHNRTcUoL/7J+pxlaCGYpsU1rHOOCr99HaWCZ2aed UPEo6W9QwPjCVLD7JPFKA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdefgeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceurghi lhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfevfhfhjggtgfesthekredttd dvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghv vghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpefgudefkefhveefle evieeuveehvdduudekuddvvdelhfeuueeijedtuedvvedvueenucffohhmrghinhepphho shhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdp nhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepghhurh husehunhhigigrrhgvrgdruggvpdhrtghpthhtohepphhgshhqlhdqghgvnhgvrhgrlhes lhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 1 Apr 2026 11:14:10 -0400 (EDT) Message-ID: Date: Wed, 1 Apr 2026 08:14:10 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: malformated LSB header in postgres: missing LSB end marker, aborting To: Matthias Apitz Cc: pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 4/1/26 12:32 AM, Matthias Apitz wrote: > El día miércoles, marzo 25, 2026 a las 07:35:21a. m. -0700, Adrian Klaver escribió: > >> From the contrib script: >> >> "# Proper init scripts on Linux systems normally require setting lock >> # and pid files under /var/run as well as reacting to network >> # settings, so you should treat this with care. >> " > > I've read this comment in the script before filing my question. And my > question is: Why postgresql.org does not deliver this PGDG Debian/Ubuntu > version of the script for Linux(!) as default: Because there are more flavors of Linux then the Debian family? The basic issue is that the project itself takes responsibility for delivering the source. Integration of the source with OS'es is left to others. What you see here: https://www.postgresql.org/download/ is delivered by separate packaging teams. At this point end users directly building from source is, from what I understand, a very small subset of the Postgres user base. The expectation is that you will be installing from some sort of packaging system or using a pre-installed service. > >> >> From the start script that the PGDG Debian/Ubuntu packages use: >> >> ### BEGIN INIT INFO >> # Provides: postgresql >> # Required-Start: $local_fs $remote_fs $network $time >> # Required-Stop: $local_fs $remote_fs $network $time >> # Should-Start: $syslog >> # Should-Stop: $syslog >> # Default-Start: 2 3 4 5 >> # Default-Stop: 0 1 6 >> # Short-Description: PostgreSQL RDBMS server >> ### END INIT INFO >> >> [Continued] > > Thanks > > matthias > -- Adrian Klaver adrian.klaver@aklaver.com