Date: Mon, 23 Jul 2012 11:24:46 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: ming.zym@gmail.com Cc: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>, "hackers@FreeBSD.org" <hackers@freebsd.org> Subject: Re: trafficserver and raw disk access in FreeBSD Message-ID: <3DBCD360-4616-4EC5-B031-B70BBC79102E@gsoft.com.au> In-Reply-To: <1343008044.4047.19.camel@zym6400> References: <1342963441.4162.8.camel@zym6400> <alpine.BSF.2.00.1207221702240.2621@wojtek.tensor.gdynia.pl> <1343008044.4047.19.camel@zym6400>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_056321EB-8B5F-4085-9F6B-C0BA391007EC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 23/07/2012, at 11:17, ming.zym@gmail.com wrote: > yeah, rules in devfs always work. and it may introduce more challenge = on > operation management, is there any way that we can do it more clean? >=20 > should we set the permission for :operator g+w on disks and = partitions? > then we can put a dedicate user for trafficserver into operator group. I would change the ownership of the disk you want to use to = trafficserver. This does mean you have double configuration (ie in devfs and ATS) but I = think it's more sensible than giving operator write perms. AFAIK operator has read access so it can run dump. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --Apple-Mail=_056321EB-8B5F-4085-9F6B-C0BA391007EC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DBCD360-4616-4EC5-B031-B70BBC79102E>