How do I change the location of the "error.log" file that by default gets placed in the same folder as the install exe when performing a quiet (-q) unattended install?
Since install4j, there the installer and custom installer applications have a "Log file for stderr" property. By default, it is set to ${compiler:sys.mediaFileName}_error.log.
Related
When I create an MSI installer with install4j, when the installer asks for permissions (the UAC prompt), the program name for the installer is a randome set of letters and numbers (i.e. 2e5658ae.msi).
The program name should really show our application name.
Is there a way to set this value in the install4j installer settings?
We've discovered that our Linux install4j installer changes/resets target folder permission to default (755) upon uninstall.
More details below.
Before installation:
target main "app" folder does not exist
During installation:
target main "app" folder gets created with 775 Linux permissions
After un-installation:
target main "app" folder gets updated/changed/reset to have 755 Linux permissions (which is the default Linux folder permission ... at least for the default umask 022)
Since we have other files in the main "app" folder (e.g. log files not owned by install4j), it makes sense that this main folder does not get deleted upon uninstall. But what we need is to make sure the Linux permissions set on it during installation stay the same after uninstall. Otherwise, if someone tries to install the instal4j installer again, the required 775 permissions are not getting set properly on the folder (probably because install4j detects that it already exists).
Is there a way to preserve the 775 Linux folder permission upon an uninstall in case the folder is left behind?
Thank you,
Ciprian
UPDATE on 10-MAR-2021
Just to wrap up this thread, the conclusion is:
Linux permissions (directory mode) for the main installation directory (target folder) are not handled consistently between install and uninstall stages:
775 at install time (even though we are explicitly setting it to 774 in the install4j project)
this is not fixed in 8.0.11; from the change log, it seems it got fixed in 9.0.0:
"Linux/Unix installers: The configured Unix directory mode was not used for the installation directory"
755 after uninstall while leaving the main installation directory intact due to containing an extra log file (even though we are explicitly setting it to 774 in the install4j project)
this was fixed in version 8.0.7; I'm testing with 8.0.11 but we can see the matching change log under 8.0.7:
"Linux: The uninstaller could change the mode of directories that were not removed"
Full install4j changelog under:
https://www.ej-technologies.com/download/install4j/changelog.html
I'm looking for a way to extract the launchers of installers created by install4j (mainly Windows installers).
My goal is to send these launchers for inclusion on the white list of antivirus sites.
I tried to use the Executable Processing option, but this operation takes place before the signing of the launchers and the silent mode makes too many changes in the machine.
It's not possible to extract files from the executable without running the installer.
At build time, you can pass the
--preserve
argument to the compiler, or check the "Do no delete temporary directory" check box in the "Build" step of the installer, then the staging directory with the launchers in the %TEMP% directory will not be deleted after the compilation finishes.
Not able to install plugin its showing the below error...
C:\devbox>vagrant plugin install 'vagrant-hostmanager'
The directory where plugins are installed (the Vagrant home directory)
has a space in it. On Windows, there is a bug in Ruby when compiling
plugins into directories with spaces. Please move your Vagrant home
directory to a path without spaces and try again.
Ruby (language used by Vagrant) has "issues" with directory names that contain spaces.
Vagrant will use an environment variable (supplied by windows) to tell it where your user directory is (so it can decide where to put your "home" directory). But you might have a space in your user name (I do) which causes a problem for ruby (which is doing the work to install the plugin).
The solution is to move your project to a project directory you choose that doesn't have any spaces in the directory name. Then, use an environment variable called VAGRANT_HOME and set it to a specified directory. The plugin installation procedure will check for the existence of this variable and use it if it exists instead of locating a home directory within the windows current user directory.
I created a folder called home within C:\Hashicorp\Vagrant and used that (C:\Hashicorp\Vagrant\home).
Setting windows environment variables is not hard (rather trivial actually) - you can find out how here: http://www.computerhope.com/issues/ch000549.htm
You'll have to do a restart to your system for it to take effect (it all worked after a reboot for me).
I've found a slight variation to the #Reinsbrains answer. In order to have a home directory without spaces within its name. I created a junction to my user/home directory. In my case I decided to go with a Linux style structure, but any location would work. In an admin command prompt:
mkdir c:\home
mklink /j c:\home\maarten "c:\users\Maarten Bicknese"
Next set the VAGRANT_HOME environment variable to the newly created junction.
setx VAGRANT_HOME c:\home\maarten
Fire up a new command prompt and you're good to go!
I have already installed the tptp from eclipse's "install new software". In the next step I shoud install the agent controller.
I've downloaded the agent controller 4.7.2 und unzipped it. According to the instruction I should now:
"Run SetConfig.bat script from a command shell in the \bin directory to generate the configuration file for the Agent Controller."
When I type the SetConfig.bat in the cmd it says that setconfig.bat is not found. I have checked the bin folder and there is no such file. So I don't know what to do.
The instruction also says: "The script requires that a Java Virtual Machine (JVM) be present in the PATH environment variable." Maybe this causes the problem? But I don't know how to set the jvm into the path variable. I use win7
What should I do now? Thanx in advance!
When there is no setconfig.bat in your bin folder chances are that you are using a non-windows distribution of the agent controller, especially if it contains setconfig.sh instead.
Please check and download the correct version if this is the cause.