Not able to read localconfig during Bugzilla installation - linux

I am newbie to testing.
I am trying to install Bugzilla.
when i enter command:
./checksetup.pl
It shows following at the end:
Reading ./localconfig...
./localconfig: Permission denied at Bugzilla/Install/Localconfig.pm line 250, line 749.
can not understand this
can anyone explain?

Bugzilla is trying to create a file named localconfig in the current directory, however you don't have access to write to that directory.
Make sure you are running checksetup.pl from the Bugzilla directory (cd /path/to/bugzilla; ./checksetup.pl), and your current account has write access to that directory.
Thanks & Regards,
Alok

Related

"bash: No such file or directory" but the file exists

I'm trying to run a specific file using the code below on desktop ubuntu
source /mnt/d/Xilinx/Vivado/2021.1/settings64.sh
However, I keep getting hit with
-bash: D:\Xilinx\DocNav\.settings64-DocNav.sh: No such file or directory
-bash: D:\Xilinx\Vivado\2021.1\.settings64-Vivado.sh: No such file or directory
-bash: D:\Xilinx\Vitis\2021.1\.settings64-Vitis.sh: No such file or directory
-bash: D:\Xilinx\Model_Composer\2021.1\.settings64-Model_Composer.sh: No such file or directory
-bash: D:\Xilinx\Vitis_HLS\2021.1\.settings64-Vitis_HLS.sh: No such file or directory
I'm confused as to why can the file not be found when I can see it existing in the folder and when I run an ls command
Here is an image of the command prompt
I have seen a few posts with similar problems but I don't quite understand their solutions. Any clarification would be appreciated.
settings64.sh file contents
source 'D:\Xilinx\DocNav\.settings64-DocNav.sh'
source 'D:\Xilinx\Vivado\2021.1\.settings64-Vivado.sh'
source 'D:\Xilinx\Vitis\2021.1\.settings64-Vitis.sh'
source 'D:\Xilinx\Model_Composer\2021.1\.settings64-Model_Composer.sh'
source 'D:\Xilinx\Vitis_HLS\2021.1\.settings64-Vitis_HLS.sh'
can you check the fill content of settings64.sh.
Because in Linux we don't mount volumes with letters like C:// or D://
According to me that script is not made for the supported OS you running on.
Let me know if I am wrong and I will edit the answer accordingly.

Changing file permission of a linux directory in install4j

I am new to install4j and am trying to change the file permission of a directory to 0750 on a project that I inherited. I am in the Define Distribution Tree screen, right click on the directory, select Edit Entry, and change the Unix mode to 750. I save the project. After running the new install (running as root), the file permission is set to 755 (default). Are there additional steps required? I looked for other spots where the file permission may have been explicitly set, but did not find any. Any ideas on what I did wrong and how to debug this? Thanks.

Lsyncd did not create a lsyncd.pid file

I just installed lsyncd-2.1.5 on a CentOS 6.4 server. I was able to run make and make install on the distribution to compile the daemon. I was able to setup the following configure file at /etc/lsyncd.lua. I was able to setup the daemon file at /etc/init.d/lsyncd. I was also able to setup the logs correctly. However, when I go to run start command on lsyncd, it throws the error:
/bin/bash: line 1: Illegal Insruction /usr/local/bin/lsyncd -pidfile /var/run/lsyncd.pid /etc/lsyncd.lua
I checked at /var/run for the file lsyncd.pid and this file was not created by lsyncd.
Any thoughts on what I should do here? Can I get this file created? Do I have to reinstall?
Let me know if I can provide any further information.
Here is what I did to solve this issue. I removed all instances of my lsyncd distribution. I had previously downloaded and compiled my package in the folder /var/tmp, so I now navigated to the root folder and ran my download command here. I un-tarred the package, and compiled the package in the root folder and setup all of my configuration files. After I started the service now, the lsyncd.pid file was now in the /var/run folder. Very strange. Can anyone tell me what the difference is between compiling in the root or /var/tmp?
Or is this possibly a situation where something possibly went wrong the first time around? Does anyone have any insight on this?

How to Fix open for write P4 ERROR?

I am having difficulty getting rid if the following error:
bash-3.00$ p4 login
Enter password:
Fatal client error; disconnecting!
open for write: /home/myuserid/tmp.17236.3: No such file or directory
The file does not exist nor do I know why it ever did.
How can I clear this?
Thanks
There are a couple of environment variables that might be at play. They control the temp location that Perforce uses for intermediate files, and also the location of the tickets file that contains the login tickets. As Bryan mentioned you should run 'p4 set' and look at your Perforce-related environment.
This was a permission issue on my home directory.
Once the home directory was created correctly the issue was resolved
Right-click cmd.exe
"Run as Administrator"
try your command again

error: ./dist/configure line 40:conf19087.sh: No such file or directory

I get the error as above when trying to build Berkeley database version 4.5.20. I have unzipped the archive to /opt on UNIX. Please can anyone tell me what I need?
I do the following:
Uncompress berkeley-db package in
some directory. say in /opt
cd to the build_unix directory
../dist/configure
When I run the last command it gives me the error as above. Does anyone know what I am missing here? Options? Another download?
Please make sure that you have correct file permissions for the distribution folder.
Try chmod +w -R /opt/db-4.5.20

Resources