All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Cain <cain@cshl.org>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: FC3, Apache and CGI web app
Date: Thu, 03 Feb 2005 10:48:48 -0500	[thread overview]
Message-ID: <1107445729.3307.28.camel@localhost.localdomain> (raw)
In-Reply-To: <420244C4.8060509@redhat.com>

On Thu, 2005-02-03 at 10:35 -0500, Daniel J Walsh wrote:
> No but you could just change the context of tmp to httpd_sys_content_t
> 
> chcon -R httpd_sys_content_t /var/www/html/gbrowse/tmp
> 
> Which should fix it. 
> 


[scott@localhost gbrowse]$ sudo chcon -R httpd_sys_content_t /var/www/html/gbrowse/tmp
/usr/bin/chcon: invalid context: httpd_sys_content_t

Is there a typo in there somewhere?  Also, is this documented somewhere?
`man` and `info` are particularly terse and not very helpful.

Thanks,
Scott


-- 
------------------------------------------------------------------------
Scott Cain, Ph. D.                                         cain@cshl.org
GMOD Coordinator (http://www.gmod.org/)                     216-392-3087
Cold Spring Harbor Laboratory


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2005-02-03 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 21:07 FC3, Apache and CGI web app Scott Cain
2005-02-02 23:46 ` Daniel J Walsh
2005-02-03  4:30   ` Scott Cain
2005-02-03 14:51     ` Daniel J Walsh
2005-02-03 15:25       ` Scott Cain
2005-02-03 15:35         ` Daniel J Walsh
2005-02-03 15:48           ` Scott Cain [this message]
2005-02-03 15:52             ` Stephen Smalley
2005-02-03 15:59             ` Daniel J Walsh
2005-02-03 16:01               ` Scott Cain
2005-02-03 16:11                 ` Daniel J Walsh
2005-02-03 16:57                   ` Scott Cain
2005-02-03  3:01 ` Colin Walters

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1107445729.3307.28.camel@localhost.localdomain \
    --to=cain@cshl.org \
    --cc=dwalsh@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.