Hi Felix,
I finally understood why it was working for the RPM.
The default permissions are set for the 'apacheds' with this line in the spec:
%defattr(-,apacheds,apacheds,-)
Except for the '/etc/init.d/apacheds' file which is executable and owned by root:
%config %attr(0755, root, root) /etc/init.d/%{name}
So I think, I can overwrite the default permissions set by the .deb and .bin installers with a 'chown apacheds:apacheds' (as you suggested) in a post-installation script.
Thanks,
Pierre-ArnaudOn Mon, Mar 31, 2008 at 3:16 PM, Felix Knecht <felixk@apache.org> wrote:
Pierre-Arnaud Marcelot schrieb:
> Thanks Guys,Just create in the rpm the locations you want to write those pids and
>
> I managed to log in as apacheds with the "sudo su - apacheds" command.
>
> I tried to run the server using the command that launches the init
> script (I already tried that under my own account but I could not test
> it under the 'apacheds' user as I could not log in as 'apacheds').
> I still had no log.
> I added write permissions for anyone to the wrapper log file, and I
> finally had one log... :D
> The log indicates that the pid file could not be created (Permission
> denied). This was something I was suspecting.
>
> Now my question are:
> Do I need to add special rights/permissions to the 'apacheds' user ?
> And more importantly:
> How the hell does it seem to work out of the box for the rpm? (and I'm
> exactly doing the same thing)
log files and give them the permission they need.
chown apacheds:apacheds probably.
>
> Thanks,
> Pierre-Arnaud
>
> On Mon, Mar 31, 2008 at 2:58 PM, David Montag <davmo024@student.liu.se
> Sorry, I think I misunderstood the question. Carry on :)
>
> /David
>
>
> On Mon, Mar 31, 2008 at 2:53 PM, Felix Knecht <felixk@apache.org
> > <mailto:felixk@apache.org <mailto:felixk@apache.org>>>> Alex Karasulu schrieb:
> > Yeah the init script will be run as the root user on
> startup. So sudo
> > su - apacheds will not require a password.
> >
> > Alex
> >
> > On Mon, Mar 31, 2008 at 8:26 AM, David Montag
> <davmo024@student.liu.se <mailto:davmo024@student.liu.se>
> > <mailto:davmo024@student.liu.se
> <mailto:davmo024@student.liu.se>>> wrote:
> >
> > Hi,
> >
> > When I tried using an installer, I had to enter the apacheds
> > user's password when starting the server using
> > /etc/init.d/apacheds start default. Maybe this is more
> or less
> > what Felix said?
> >
> Alex is right, there should be no need to enter a password
> and
> No, not exactly what I meant. I tried to say to execute the
> init script
> manually step by step and see where it fails ;-)
>
> Felix
>
> >
> > /David
> >
> >
> > On Mon, Mar 31, 2008 at 2:05 PM, Felix Knecht
> <felixk@apache.org <mailto:felixk@apache.org>
> wrote:
> >
> > Pierre-Arnaud Marcelot schrieb:
> > > Hi,
> > >
> > > I'm trying to finish the new installers (.deb and
> .bin), and I'm
> > > facing an issue when I'm trying to run Apache DS
> with an
> > 'apacheds' user.
> > >
> > > I looked at the RPM Spec file
> > >
> (/installers/apacheds/src/main/installers/apacheds-rpm.spec)
> > used to
> > > build the RPM package and I've seen that it
> creates a group
> > and a user
> > > called 'apacheds' on the target system and that
> the init
> > script uses
> > > this 'apacheds' user to run the server.
> > >
> > > I added the same thing in the .deb and .bin
> installer. The
> > user and
> > > group 'apacheds' are well created but launching
> the server
> > does not
> > > work as expected, letting me with no log in the
> wrapper, nor
> > the server.
> > >
> > > If anyone has an idea...
> > Maybe this helps to get more error messages:
> >
> > Try after installation to sudo su - apacheds and
> start the server
> > manually (not from the /etc/init.d script but what
> the script
> > does.
> >
> > I could imaging missing permissions on files or missing
> > $JAVA_HOME or so
> > ....
> >
> > Felix
> >
> > > Chris maybe, as you designed the RPM Spec.
> > >
> > > Thanks,
> > > Pierre-Arnaud
> >
> >
> >
>
>
>