create a pseudo user ‘rt’ and chown the directory to rt &
ensure that rt-mailgate runs as a user with permissions to
write to that directory & the directory permissions are
apropriately set. If ‘rt-mailgate’ runs a root or rt the
0700 should do.
well, it was all rt:rt before. then i gave me this same error and i switched
it to nobody (to no effect)
What are your permissions set to??
mAX
-----Original Message-----
create a pseudo user ‘rt’ and chown the directory to rt &
ensure that rt-mailgate runs as a user with permissions to
write to that directory & the directory permissions are
apropriately set. If ‘rt-mailgate’ runs a root or rt the
0700 should do.
is there any other file involved on the process you need to know the
permissions?
mAX
-----Original Message-----
when I asked for permissions I meant just that not the ownership.
I think using the -R option with chown might have been a mistake
should have picked up on it sooner. (Its after midnight & I’m
still working on a report needed yesterday) Permissions & ownership vary
throughout the directory tree.
e.g.
peony 00:30:49 /usr/local/rt/bin: ls -l
total 21
drwxr-xr-x 2 rt rt 1024 May 1 2000 cgi
lrwxrwxrwx 1 root root 30 May 1 2000 rt →
/usr/local/rt/bin/suid_wrapper
lrwxrwxrwx 1 root root 30 May 1 2000 rt-mailgate →
/usr/local/rt/bin/suid_wrapper
lrwxrwxrwx 1 root root 30 May 1 2000 rtadmin →
/usr/local/rt/bin/suid_wrapper
-rwxr-xr-x 1 rt rt 2104 May 1 2000 rtmux.pl
-rwxr-xr-x 1 rt rt 2167 Apr 26 2000 rtmux.pl.orig
lrwxrwxrwx 1 root root 30 May 1 2000 rtq →
/usr/local/rt/bin/suid_wrapper
—s–x–x 3 root rt 12780 May 1 2000 suid_wrapper
you may notice suid_wrapper is run setuid & is owned by root & this
could be the core of your problem.
& in another part of the tree where some storage occurs.
peony 00:36:16 /usr/local/rt/transactions/2000: ls -l
total 3
drwxr-x— 5 rt rt 1024 Apr 23 2000 Apr
drwx------ 3 root daemon 1024 Dec 7 00:06 Dec
drwx------ 4 root nogroup 1024 May 12 2000 May
I think this shohuld help you on your way. Please don’t ask
why ownerships are different as I have NFI:-(
In any case some sort of consistency is essential & the other
thing to watch out for is to ensure you don’t lock yourself
out of MySQL by changing who rt runs as though I expect this
is determined by suid_wrapper.
| it is all set to user “rt” and group “rt”
|
| still i get the annoying:
| “Can’t create output: Permission denied”
±–>8
Make sure suid_wrapper is owned by rt and setuid. Also make sure the
“transactions” directory and all subdirectories are writeable by the owner.
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university [“better check the oblivious first” -ke6sls]
Give your computer something to dream about. (tm)
Popular Power - www.popularpower.comOn Wed, 6 Dec 2000, Brandon S. Allbery KF8NH wrote:
On Wednesday, December 06, 2000 10:38 -0200, Max Mismetti max@mediaworks.com.br wrote:
±----
| it is all set to user “rt” and group “rt”
|
| still i get the annoying:
| “Can’t create output: Permission denied”
±–>8
Make sure suid_wrapper is owned by rt and setuid. Also make sure the
“transactions” directory and all subdirectories are writeable by the owner.
–
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university [“better check the oblivious first” -ke6sls]
I’m getting a response of ‘Permission denied’ when from an external
client I’m trying to respond to a ticket.
This was working OK - very unlike these sorts of systems to be
inconsistant?!?
I really hate that error… hard to troubleshoot, but here’s what I
learned… (Hmmm I think I should put this in the wiki)
Email addresses are used for auto-created accounts. Make sure the
email address in a reply is the same as the original ticket.
If tickets are moved to a new queue, make sure that the “requestor”
group has privs to respond in new queue! ( this was our problem )
RT logs using the SYSLOG mechanism… check your log for clues…
remember to focus on email addresses.