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
Related
I updated to the version here where it installs it per user instead of all.
How do I install for all users instead? Do I need to install for each user now?
Look for the system installer instead of the user setup installer. The system installer will give you the option to:
1. Install for all users
2. Choose a directory.
Download here (oficial page): https://code.visualstudio.com/download
Can't find it? The system installer is below the big blue button to download. You'll see 3 options. The middle option will say system installer.
Applications that are global are stored in /Applications directory as opposed user specific installation that are installed under Applications under the user home directory. So moving the installed folder to /Applications directory might work.
I might have installed the wrong version of Oracle SQL Developer (Version 4.1.4) on my Win 10 laptop. So I want to uninstall it and install a newer version.
Any idea what´s the easiest way to do it?
Find the directory it was unzipped to, e.g. C:\Program Files\sqldeveloper, though it could be anywhere - quite likely in your downloads directory; and just delete that entire sqldeveloper directory.
There is no installation as such, it's just a Java application sitting in a directory.
Settings are held under your personal home directory, and when you unzip and run the later version (18.2 is current) you'll be asked if you want to migrate those settings, which will include any connections you've already defined.
Read more in the 4.1 documentation.
It is not installed so you can't uninstall it. To remove it from system do following:
Delete base directory, where you unziped it (where you run it).
Delete your user connection data - folder C:\Users\<username>\AppData\Roaming\SQL developer
If you don't have any other oracle software, delete your user configuration data - folder C:\Users\<username>\Oracle
where can I find or develop *.erl files on my server after installation kazoo 2600hz I can't see any .erl file !
I installed kazoo correctly and it work
but I cant find files to develop
is this about permission?
The Kazoo RPM installs its files under /opt/kazoo. You will find the .erl files in sub directories under this folder. You can update the source, run make in the appropriate directory (i.e. the first folder with a Makefile up from the .erl file you edited) and then restart the service to run your changes.
I'm on a Windows 7 (64-bit) box and do not have admin rights.
It appears from the MongoDB download page (see http://docs.mongodb.org/manual/tutorial/install-mongodb-on-windows/) that the latest version only an MSI install is available (no zip version).
I tried running the 3.0.4 MSI. I clicked custom so I could change the directory to install to. I used %USERPROFILE%\MyProgs\MongoDB-3.0.4, so no admin rights would be needed. It ran for a bit but then prompted me to enter admin credentials. I hit escape (like clicking on X at top right) to close the window. On other MSI installs this has worked. I tried it again and clicked "No" but in both cases received the message
MongoDB 3.0.4 2008R2Plus SSL (64 bit) setup was interrupted.
Your system has not been modified. [...]
This article does a GREAT job going through how to install MongoDB on Windows:
How to install mongoDB on windows?
My observation is that v2.4.14 is the last version that is available via the ZIP format. So for now, I'm using that version.
Is there any other way to install the MongoDB version 3.X MSI without admin rights?
NOTE: On the MongoDB Download page https://www.mongodb.org/downloads there is a link titled View Build Archive (it sends you here https://www.mongodb.org/dl/win32/x86_64-2008plus-ssl, and that site lists *.zip formatted files). I thought I had found my own solution to the question, but when I unzipped the files, and added the "bin" to my path and ran the programs (mongo, and mongod) I received an Windows Dialog that says:
mongod.exe - System Error
The program can't start because LIBEAY32.dll is missing from your
computer. Try reinstalling the program to fix the problem
I stopped here and posted this question. Thanks for any help.
For now I'm using the version that supported the zip format (v2.4.14) and that version does work.
NOTE2: The v2.4.14 zip formatted install doesn't have a file named LIBEAY32.dll), or I might have tried using that file with the newer version.
Yes, it is possible to install the latest MSI (including the one with SSL) without admin rights via command line.
msiexec /a mongodb-win32-x64-3.2.5.msi /qb TARGETDIR="C:\MongoDB"
This will copy the binaries into C:\MongoDB\MongoDB\Server\3.2\bin
I dislike long paths like that, so I create a symlink inside the folder:
cd C:\MongoDB
mklink /j bin C:\MongoDB\MongoDB\Server\3.2\bin
That will create a soft link as C:\MongoDB\bin (which you can add to your PATH environment variable).
mongo --version
mongod --version
Both should return version 3.2.5.
You can do this with most packages, we have to do similar with Python 2.7 and Node 4.4.3 MSI packages on work computers that do not have admin rights.
You can download the "legacy" version which is the unsigned non msi version as a zip. The disclaimer is listed as
The 64-bit legacy build does not include SSL encryption and lacks
newer features of Windows that enhance performance. Use this build for
Windows Server 2003, 2008, or Windows Vista
The 3.0.5 version is https://fastdl.mongodb.org/win32/mongodb-win32-x86_64-3.0.5.zip
The latest version is available as zip download.
[https://www.mongodb.com/dr/fastdl.mongodb.org/win32/mongodb-win32-x86_64-2008plus-ssl-4.0.6.zip/download][1]
Download and Unzip into folder where user has permissions e.g c:\users\xxx\mongodb.
Enter the path to bin folder (e..g c:\users\xxx\mongodb\bin) into the
environment variable 'PATH'. To access path variable press Win + R
and then enter rundll32 sysdm.cpl,EditEnvironmentVariables.
Select Path and click edit. Then enter new and there enter the path
to bin folder. Click OK and OK to save and exit.
Check Mongo version from command line using command mongo --version.
Note: Don't forget to create db folder in C drive that is required for mongo to work locally. All set.
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!