| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
- Fix and test the Erlang code.
- Do not export_all.
|
| | |
|
| |
|
|
| |
Bring back Solaris' ucb PATH just in case.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A bunch of fixes:
* Only try to find out the user that is running the script if
that's necessary. That allows us to error out if we can't find
the user name.
* Fallback to 'whoami' in the unlikely case that 'id -un' does
not work.
* Use 'su' if 'sudo' is not installed, and if the user is 'root'.
(The 'sudo' binary is not installed by default in many OSs.)
|
| |
|
|
|
|
|
|
|
| |
'whoami' is not POSIX-compliant, but 'id -un' is. This is true
at least since the 1003.1-2001 standard, I don't have a copy of the
previous 1003.2-1992 to verify it is true there too.
This causes problems in recent operating systems where 'whoami' is
not even shipped anymore.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Build project-specific PLT
$ rebar build-plt
Check the PLT for consistency and rebuild it if it is not up-to-date
$ rebar check-plt
Analyze the code for discrepancies
$ rebar dialyze
Delete project-specific PLT
$ rebar delete-plt
Valid rebar.config options:
%% Store PLT in ~/.rebar/plt (Default)
{dialyzer_plt_location,shared}
%% Store PLT locally inside the project in .rebar
{dialyzer_plt_location,local}
%% Store PLT in custom directory
{dialyzer_plt_location,"custom_path"}
{dialyzer_plt_extra_apps,[app1,app2]}
{dialyzer_warnings,[unmatched_returns,error_handling]}
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Implemented, by moving upgrade functionality from install_upgrade.escript
to nodetool, which already supports both short and long names.
Make install_upgrade.escript as wrapper for nodetool for backward compatibility.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When -p/--profile is enabled, you can select the profiler as follows:
generate flame graph (eflame.svg) from trace (eflame.trace)
$ rebar -p compile profiler=eflame
generate fprof.analysis
$ rebar -p compile
generate fprof.analysis
$ rebar -p compile profiler=fprof
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
When a node is configured with -sname the REMSH_NAME_PART argument should be defined with using command 'hostname' but error occurs due extra space
|
| |\
| |
| | |
Slim release support
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Always-on recursive application of all rebar commands causes too many
issues. Recursive application is required for:
1. dealing with dependencies: get-deps, update-deps, and compile of deps
right after get-deps or update-deps
2. projects with a riak-like apps/ project structure and dev process
The vast majority of projects are not structured like riak. Therefore,
moving forward it's best to (by default) restrict recursive behavior to
dealing with deps. This commit does that and also adds command line and
rebar.config options for controlling or configuring recursion. Also, we
introduce two meta commands: prepare-deps (equivalent to rebar -r
get-deps compile) and refresh-deps (equivalent to rebar -r update-deps
compile). riak-like projects can extend the list of recursive commands
(to include 'eunit' and 'compile') by adding
{recursive_cmds, [eunit, compile]} to rebar.config.
|
| |\
| |
| | |
Incorrect REMSH args when sname is used.
|
| | |
| |
| |
| |
| | |
To avoid problems with REMSH node being visible from another nodes
starts it in hidden mode (erl -hidden).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a node is configured with -sname in app.config or sys.config the
REMSH_NAME_ARG and REMSH_REMSH_ARG arguments are incorrect due the
assumption that the node name always contains '@'.
To fix the bug, the script tries to find '@' and then compose the
arguments acording to node name type. If in long name mode the
script can't compose a correct node name exits with warning.
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
RUNNER_SCRIPT variable is not initialized in simplenode.runner and it's
referenced when calling sudo.
|
| |\
| |
| | |
Remove leading empty line from a template
|
| | | |
|
| |\ \
| | |
| | | |
Use "pwd -P" to get the current physical path.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It is a portable version of the realpath(1) utility that you can find on
Mac OS X and FreeBSD (see also The Open Group Base Specifications Issue
6, IEEE Std 1003.1).
Without the -P flag, pwd(1) might return different values when the
current path contains one or more symlinks, depending on how you got
into the current directory.
In simplenode.runner, this may cause PIPE_DIR to have different values
on each use, which will make it impossible to connect to the running
node unless you guess the correct path yourself.
|
| |/ / |
|
| | |
| |
| |
| | |
This removes the dependency on lib/compiler in an OTP release.
|
| | |
| |
| |
| |
| |
| | |
As discussed here
http://erlang.org/pipermail/erlang-questions/2012-December/071135.html
change the reltool spec to use the default sys-level mod_cond setting.
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
When developing Riak, we have found bugs and other issues due
to the number of platforms we support.
Here is an overview of the changes:
- Fix command-line syntax for commands to work on *BSD / Sun
- Add chkconfig and getpid to nodetool
- Replace platform specific 'kill' commands with a nodetool
getpid method
- Fix RUNNER_USER settings to work on *BSD
|
| |\
| |
| | |
Add missing variables
|
| | |
| |
| |
| | |
- add overlay_vars=, target_dir=, and tests= with short description
|
| |/
|
|
|
| |
- add missing short and long options
- add tests=, target_dir=, overlay_vars=
|
| | |
|
| | |
|
| |\
| |
| | |
Change zsh completion script
|
| | |
| |
| |
| |
| | |
- Add 'escriptize' command
- Remove variable 'dump_spec'
|
| |/ |
|
| | |
|
| |
|
|
| |
For enable to shell-completion in zsh.
|
| | |
|
| | |
|
