From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/640 Path: main.gmane.org!not-for-mail From: Anthony Baker Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Invoking runsvctrl as non-root Date: Wed, 01 Dec 2004 08:10:38 -0800 Message-ID: <1101917438.3060.239.camel@localhost.localdomain> References: <1101863206.3060.236.camel@localhost.localdomain> <41AD88D5.8040504@physics.ox.ac.uk> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1101919497 19176 80.91.229.6 (1 Dec 2004 16:44:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 1 Dec 2004 16:44:57 +0000 (UTC) Original-X-From: supervision-return-879-gcsg-supervision=m.gmane.org@list.skarnet.org Wed Dec 01 17:44:50 2004 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14] ident=qmailr) by deer.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 1CZX3x-0007lb-00 for ; Wed, 01 Dec 2004 17:10:42 +0100 Original-Received: (qmail 20189 invoked by uid 76); 1 Dec 2004 16:11:02 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 20183 invoked from network); 1 Dec 2004 16:11:02 -0000 Original-To: supervision@list.skarnet.org In-Reply-To: <41AD88D5.8040504@physics.ox.ac.uk> X-Mailer: Ximian Evolution 1.4.6 Xref: main.gmane.org gmane.comp.sysutils.supervision.general:640 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:640 On Wed, 2004-12-01 at 01:03, Ian Stokes-Rees wrote: > >>I'm running into a permissions issue trying to invoke runsvctrl as a > >>non-root user > > > > As the message implies, you need to give some permissions to the > > user you want to allow runsvctrl and runsvstat -- most particularly, write > > access to the socket ./supervise/control and read access to ./supervise/ok > > and ./supervise/status. > > The trick is to manually change the access permissions, so other users > can access the service. Make sure they are the users you want to be > able to access the service! I am pretty sure those permissions will > stick and runit won't overwrite them, unless the > directories/files/sockets are deleted and re-created. UMASK might come > into play here, but I'm not sure. > Thanks for the suggestions, a "chown" in the run script prior to exec did the trick. Anthony