From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.66.100.200 with SMTP id fa8mr21333556pab.31.1422959514107; Tue, 03 Feb 2015 02:31:54 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.140.81.85 with SMTP id e79ls2933804qgd.46.gmail; Tue, 03 Feb 2015 02:31:53 -0800 (PST) X-Received: by 10.140.92.146 with SMTP id b18mr288869qge.36.1422959513920; Tue, 03 Feb 2015 02:31:53 -0800 (PST) Date: Tue, 3 Feb 2015 02:31:52 -0800 (PST) From: Stefan Beyer To: voidlinux@googlegroups.com Message-Id: In-Reply-To: References: <0d9aa61f-ac00-491c-a262-c9e27b5057fa@googlegroups.com> Subject: Re: How to downgrade? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_3392_1325811880.1422959512244" ------=_Part_3392_1325811880.1422959512244 Content-Type: multipart/alternative; boundary="----=_Part_3393_629945888.1422959512244" ------=_Part_3393_629945888.1422959512244 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Am Dienstag, 3. Februar 2015 11:15:30 UTC+1 schrieb Juan RP: > > What kind of problem specifically? > Service statd does not come up: # sv status /var/service/statd down: /var/service/statd: 1s, normally up, want up # ps wax | grep runsvdir 491 ? Ss 0:00 runsvdir -P /run/runit/runsvdir/current log: rvice already running! Statd service already running! Statd service already run Removing /var/service/statd, no rpc.statd is being launched. Launching rpc.statd -F -d by hand, the process does not stay in foreground, which I believe is the cause. ------=_Part_3393_629945888.1422959512244 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
Am Dienstag, 3. Februar 2015 11:15:30 UTC+1 schrieb Juan RP:
What kind of problem specifically?

Service statd does not come up:

# sv status /var/service/statd
down: /var/service/statd: 1s, normally up, want up

# ps wax | grep runsvdir
491 ?        Ss     0:00 runsvdir -P /run/runit/runsvdir/current log: rvice already running! Statd service already running! Statd service already run

Removing /var/service/statd, no rpc.statd is being launched.
Launching rpc.statd -F -d by hand, the process does not stay in foreground, which I believe is the cause.
------=_Part_3393_629945888.1422959512244-- ------=_Part_3392_1325811880.1422959512244--