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

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

Scott Cain wrote:

>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
>
>
>  
>
Oops
chcon -R -t httpd_sys_content_t /var/www/html/gbrowse/tmp

There should be a man page, there is one on my machine



[-- Attachment #2: chcon --]
[-- Type: text/plain, Size: 1549 bytes --]

CHCON(1)			User Commands			     CHCON(1)



NAME
       chcon - change security context

SYNOPSIS
       chcon [OPTION]... CONTEXT FILE...
       chcon [OPTION]... --reference=RFILE FILE...

DESCRIPTION
       Change the security context of each FILE to CONTEXT.

       -c, --changes
	      like verbose but report only when a change is made

       -h, --no-dereference
	      affect symbolic links instead of any referenced file (available
	      only on systems with lchown system call)

       -f, --silent, --quiet
	      suppress most error messages

       -l, --range
	      set range RANGE in the target security context

       --reference=RFILE
	      use RFILE’s context instead of using a CONTEXT value

       -R, --recursive
	      change files and directories recursively

       -r, --role
	      set role ROLE in the target security context

       -t, --type
	      set type TYPE in the target security context

       -u, --user
	      set user USER in the target security context

       -v, --verbose
	      output a diagnostic for every file processed

       --help display this help and exit

       --version
	      output version information and exit

REPORTING BUGS
       Report bugs to <email@host.com>.

SEE ALSO
       The full documentation for chcon is maintained as  a  Texinfo  manual.
       If  the	info  and chcon programs are properly installed at your site,
       the command

	      info chcon

       should give you access to the complete manual.



chcon (coreutils) 5.0		  July 2003			     CHCON(1)

  parent reply	other threads:[~2005-02-03 15:59 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
2005-02-03 15:52             ` Stephen Smalley
2005-02-03 15:59             ` Daniel J Walsh [this message]
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=42024A45.8060602@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=cain@cshl.org \
    --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.