Bug 8526 - tries to create pid file in ${prefix}/run/samba.pid when run from source directory
Summary: tries to create pid file in ${prefix}/run/samba.pid when run from source dire...
Status: NEW
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: samba4-qa@samba.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-14 09:35 UTC by Matthieu Patou
Modified: 2012-02-24 15:44 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthieu Patou 2011-10-14 09:35:24 UTC 
After compiling, it can't be just run in single mode from the source directory.
At least one install is needed in order to make all the folder needed for a samba to run in single mode.

An option like make installdir would be useful to allow quick testing in a machine without the hassle of installing the whole stuff (and relinking).
Comment 1 Andrew Bartlett 2011-10-14 10:11:38 UTC 
If samba requires some installation directory to run from the build directory, then that is a bug that should be fixed.  

We already set the python and script directories, we can set others too.
Comment 2 Matthieu Patou 2011-10-15 08:53:49 UTC 
Andrew,
I'm not really sure what were the constraint but I'm pretty sure that the fact that samba always try to store its pid in /usr/local/samba/var/run/samba.pid even when it's started from the source directory, is part of the problem.