aledr wrote:
As I said: **I do not have root access** (the build service doesn't
allow to build a package as root) what means that I can't add users or
groups to the system too...

I modified the "configure" and "Makefile" to do not exit if the user /
group test fails and included "vpopmail.dir", "vpopmail.uid" and
"vpopmail.gid" to the source. It worked, but in the next releases I'll
need to do again..

How do you intend to start vpopmail?
port 110 is a privileged port, therefor it needs to have some root relation to actually start :) ...and if you just want to build it there to move adn run it on asystme you do have root on, then why not do it all there in teh first place.

I appreciate Your help.

2007/10/3, Rick Widmer <[EMAIL PROTECTED]>:
Christopher Chan wrote:
Rick Widmer wrote:
Christopher Chan wrote:
Rick Widmer wrote:
Christopher Chan wrote:
Rick Widmer wrote:
Christopher Chan wrote:
Have you created the vpopmail user and vchkpw group?  If not
you must.
Yes, I will create they when installing the package in my
host. This is the why I need to get these values into the
package when
building. The build host isn't my dest host.

That is a tough nut to crack. IIRC, vpopmail default uid/gid
conflicts with postfix on Redhat distros.
What is the problem?  Just create the group and user with
different values.  It doesn't matter what the number is, it just
has to exist when your run ./configure.
Oh, the vpopmail uid and gid is not hardcoded into the binaries?

The uid and gid are hard coded into the bianaries by ./configure.
I cannot then use them on another host where they are different then.

Well, that was the whole point of OP's post and why I said it was a
tough nut to crack. The OP wants to build a package that will be used on
other hosts...

Then use the same numbers for the uid and gid values for all qmail and
vpopmail users on all systems.
[ ]'s
Aledr - Alexandre
"OpenSource Solutions for SmallBusiness Problems"

Reply via email to