this is pretty simply caused by the RPM command running as root and then
the dir is owned by root...then if you start it as another user, that
user doesn't have permission (and shouldn't) to the dir.
If you install as root (with RPM you have to) you need to run as root or
the RPM needs to change permissions to a user which means it pretty much
has to create the user.
-Andy
Emmanuel Lecharny wrote:
Hi Ole,
can you fill a JIRA for this issue?
Thanks !
On 5/13/07, Ole Ersoy <ole....@gmail.com> wrote:
This is interesting.
After installing a fresh RPM (And deleting the old files
manually)
if I try to start ADS as root using
/etc/init.d/apacheds start
I get an OK but the server just exits right
away.
I think the reason is this:
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: apacheds-rolling.log (Permission denied)
at java.io.FileOutputStream.openAppend(Native Method)
So somehow it's not able to create the rolling log. I verified
this by looking in /usr/local/apacheds-1.5.0/
and there's no apacheds-rolling.log
However if I start the server like this:
/etc/init.d/apacheds debug
it starts fine.
I thought this was because it prints the log
to the screen so that it does not attempt to open it.
However it's also able to create the rolling log now.
I verified this. /usr/local/apacheds-1.5.0/apacheds-rolling.log
exists.
I'm surprised that only I'm getting this though. I'm running
Fedora 6 x86_64.
Cheers,
- Ole
9 messages in org.apache.directory.devRe: [Installer] Possible Bug - apache...
