Auto-start apps / services are scattered out there...
To list all Auto-Start Applications, search for autostart:
ls -1 "/etc/xdg/autostart" "/home/$USER/.config/autostart" \
To list all Auto-Start Services:
systemctl list-unit-files --type=service
# OR search for:
ls -1 /lib/systemd/system/*....
In my case, I installed two CentOS virtual machine by using VMware Player (Host OS: CentOS7). I found no IP address for both of virtual machines.
The IP address set by following the below procedures.
Check the current connection on your VM:
# nmcli con show
NAME UUID TYPE DEVICE
ens33 xxxxxx ethernet ---
The network is not ...
If you remote server has a DNS Server configured (check in /etc/resolv.conf) the SSH Server will try to do a reverse DNS lookup of the client's IP address. If it's not resolvable, it will wait for a 30s timeout to give you access. So it may be not hanging.
Also check if you can ssh from within the server (through the 127.0.0.1 local IP) to check if it ...
It might be fine to turn off Clamav services, it certainly consumes incresaly resources like cpu and memory. You should instead, use well known services/frameworks that helps to detect and alert on any unauthorized action or access into the server such as Snort or OSSEC.
A virus scanner isn't likely to do much for the local linux machine, but you might be using it to scan uploaded files from OSes that aren't so safe. Or it might be removing evil attachments from email it processes.
I say, humbly, that if you have to ask, you should leave it on.
It is chewing on something, when you see the weight of it, so it might be doing ...
Looks like the kernel has paniced (crashed), apparently when trying to get statistics from the tg3 Broadcom NIC driver. You'll need to reset the system to let it reboot again.
You probably should update the system, or at least the kernel, to CentOS 6.[latest] and see if the crash happens again. If you have any third-party driver packages, you should update ...
This worked for me:
Once you are are in emergency mode run
xfs_repair -L /dev/dm-0 && reboot
Log in and in a terminal run
sudo xfs_fsr /dev/mapper/centos-root
sudo xfs_fsr /dev/dm-0
Not 100% sure what the issue is but all my centOS VMs regardless of version does this. I was working on this issue for a week.
I had exactly the same issue on a CentOS 6 machine. For me an reinstall worked:
sudo yum remove python-pip
sudo yum install python-pip
then I was able to verify that it work via:
pip 7.1.0 from /usr/lib/python2.6/site-packages (python 2.6)
common mistake you name the file reoslve.conf vs resolv.conf,, check that the file name is resolv.conf..then type ping yahoo.com or some domain of your choosing, should resolve properly and automatically after you update this file, or try after service network start then ping.
As pointed out by R. S, the CentOS official Docker images have manual page installation disabled. This is true also of the Fedora official Docker images.
The easiest way to handle this is via the following sed command, which will work on either system:
sed -i -e '/tsflags=nodocs/s/^/#/' /etc/yum.conf /etc/dnf/dnf.conf || true
This will produce an error ...
I know it's been a while but for anyone who's looking for an answer as to why it happens: Some providers (ISP, Company VPNs, etc) send a "Transient hostname" back to the host whenever making a request for an IP via DHCP, and depending on your machine's configuration, it gets set as the current machine's hostname
My problem (and the way I ended up here) was ...
I am no developer and this answer is not great, but I hope it helps.
In trying to get Igel UMS Management interface to run on CentOS 7, I ran into the same error. For me the answer was to compile and install a newer version of GCC using the following steps.
yum install gmp-devel mpfr-devel libmpc-devel wget
Here's how a switch works:
The switch has several network ports, and those are connected point-to-point to a NIC on a computer. If the NIC can do 25 GB/s, that means that the point-to-point connection will use a protocol that does 25 GB/s.
Now with a dumb switch, that would also mean that the incoming connection routed to that NIC is restricted to 25 GB/s. ...
echo " Enter the name of your directory. You should enter the absolute path to the directory if it is not found in the current directory!" -- prints the text
read location - expects you to enter some text and stores in in a variable $location
echo $location - prints the variable $location
filecount=$(...) - stores the output of the command in a variable $...
To fix this problem, you should reinstall Python 2.7 shipped with CentOS 7.
(See below as for why you should reinstall, and how you should manage newer versions of software in a distro such as CentOS.)
Reinstalling older Python from RPM
Since yum is not working, you'll have to do most of it manually, by downloading the packages and reinstalling them using ...
history only shows the commands that have been executed in the current shell. That history has a number of drawbacks:
it might not be stored to any file if the user configures the shell not to do that;
even if it's recorded, it's in a file that is write-accessible by the user (usually ~/.history, ~/.bash_history, ~/.zsh_history or something like that). Thus,...
Recording normally means storing event info in the standard location at /var/log. There are plenty of other ways an activity leaves a trace otherwise, but those are not what she means here apparently. You can get more details in the same book in the chapter on logging (page 572 in the 5th edition).
What you see using history is recorded by the shell, not by su. su itself doesn’t record the commands that are run as root. The author might have wanted to contrast this with sudo which does log its arguments (and can even be configured to record entire sessions).
Above mentioned script used to find the pathnames of files whose size is less than 4 KB and has a filename suffix .txt.
It would not handle a value of $location that contains spaces etc. as the variable expansion is unquoted. It would furthermore store the pathnames as a single string, which would make it difficult to count them if any pathname contains ...
If you can modify the script and if you can use crontab, then you might use the @reboot timing in crontab to rerun the script. The behaviour of the script would be dual, depending on how it's called. So eg. if it's run with a parameter -s or --second-run, then it would do the after-reboot stuff. Introducing two main functions in the script like first_run and ...
Those "tutorials" are a calamity.
I'm not administering centos machines, but on my centos 7 vm test machine (yours looks like centos 6), this is how I installed nodejs:
yum install epel-release
yum install nodejs
A (completely untested) method to fix the damage would be to remove the nodejs package, remove the nodesource repository, and then install ...
Question was answered by Johnny Hughes via mailing list:
The steps are that the source code is released to git.centos.org .. in
this case, the source code was released here:
Then the source code for all the updates that happen at that time are
downloaded to our build system and built. Then we do ...
In the DHCP protocol, there are two ways to specify the PXE boot filename and the TFTP server address to load it from:
either using the legacy BOOTP fields (as DHCP is an extension of BOOTP)
or using newer DHCP options for the same purpose.
Apparently dnsmasq uses the latter method by default... and I've encountered an otherwise quite modern PXE firmware ...
In Gentoo I was able to solve this problem by adding
at the end of the file /etc/default/grub
It is important that you add the prefix gfx- in front of the actual resolution. Otherwise this won't work.
If you want to find out which resolutions are possible, you might want to start with
if you google images "centos 7 software selection options" you will see a pic showing all the choices available for "Base Environment" which include "Minimal Install (basic functionality)" and "Gnome Desktop" and "Server with GUI". My recommendation would be to do "Server with gui" because that will basically install and allow all software that could ...
I'm a bit late to the party but asked myself the same question today and came to the following conclusion:
This is against the principle of least privilege and should therefore be avoided.
More specifically this might give the user (read, write or exec) permissions not only to a lot of regular files and directories but also lots of special ones like that ...
A few points here::
First, remove noauto, because that would prevent mount -a from working.
Then also check if the "T" bit is set on /media/dvd, such as
chmod +t /media/dvd
This will set the sticky bit on the dvd directory so that anybody can write to it and own and be able to remove modify only his/her files directories.
In addition, CAP_SYS_ADMIN Linux ...
I would recommend to create link post successful installation instead of during, create link in %post section for rpm build.
Something link below
ln [OPTION]... [-T] TARGET LINK_NAME
This is a complex issue because the two are not compatible for multiple reasons and so direct conversion from one to the other is generally very tricky.
A little background
apt (apt-get) is a package manager for installing Debian style .dpkg packages and their dependencies.
yum is a package manager for installing red-hat .rpm style packages and their ...
I suppose that the part that is causing you trouble is this:
# Install dependencies
sudo apt-get install git bc i2c-tools fonts-freefont-ttf whiptail make gcc -y
# For Python 2
sudo apt-get install python-pil python-smbus python-dateutil -y
# For Python 3
sudo apt-get install python3-pil python3-smbus python3-dateutil -y
First I would suggest making sure ...
I think the problem is that you are storing the “imjournal.state” file in the wrong location, so SELinux is blocking writes. Rather than creating a custom policy module that grants too much permissions, you should use the default location, which is /var/lib/rsyslog. The default config says:
You have a damaged .so.
In general, you issue the following command to find the package it belongs to:
yum provides \*/<so_file>
In your case:
$ yum provides \*/libgcc_s.so.1
libgcc-4.4.6-4.el6.i686 : GCC version 4.4 shared support library
Repo : base
Filename : /lib/libgcc_s.so.1
In this case, we want libgcc-4.4.6-4.el6....
You can set a forwared port from localhost to guest machine, it has to work for sure:
Vagrant.configure("2") do |config|
config.vm.network "forwarded_port", guest: 9200, host: 9200
curl -X GET http://localhost:9200
When using public network configuration a bridge interface with host machine ethernet adapter will be added, and you need to set up IP ...
You may want to try script:
script -c target output.log
This would start the command target and save a transcript of the whole session, until target terminates, into the file output.log. If the command (your target) is several words long, quote the full command.
See the manual for script (man script).
If you can't change the target command itself, then this should be helpful:
target | tee output.bak
output.bak will contain a copy of all the output (just stdout in this example), so you'll have to trim it if you want just the initial info.
Some people would obviously accept disabling selinux, or setting it to permissive as the answer; but then there will always be a few snarky linux gurus who will chime in with the words, "stop disabling selinux!" BUT THAT IS ALL THEY WILL SAY! Quit telling people to "stop disabling selinux" UNLESS YOU ALSO TELL THEM THE SOLUTION!
Well I found the solution to ...
That looks perfectly normal.
The automounter takes over the top level directory, /srv/xray for all the mounts defined in the corresponding file or program, /etc/auto.xray. (In your case it's a normal file.)
Filesystems are only mounted on demand, so when you looked inside /srv/xray you would initially have seen nothing. But when you ran ls -ld /srv/xray/...
On CentOS (and other RPM-based distributions), you need to install the openssl-devel package:
sudo yum install openssl-devel
(Use sudo dnf ... on CentOS 8, RHEL 8 or Fedora.)
The equivalent in the Debian ecosystem is libssl-dev.
I solved the issue myself, hopefully someone else will find it usefull. I took a look at ~/.xsession-errors, it contained:
(imsettings-check:16467): IMSettings-WARNING **: 04:42:56.491: Could not connect: Connection refused
(imsettings-check:16467): GLib-GIO-CRITICAL **: 04:42:56.491: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' ...
Firstly, you're dealing with different encoding protocols: Windows encodes in UTF-16, whereas the default for Linux & OSX is UTF-8.
So although you've set the encoding to UTF-8 when mounting your pile of data in Linux, the data was encoded with UTF-16 by Windows.
I suspect the filenames contain multi-byte characters that are not being read correctly in ...
In general, CentOS patches are just new RPMs with increased version numbers. In this case, libssh2-1.4.3-12.el7_6.2.x86_64.rpm is installed, which contains all previously released patches as well (if CentOS lists them of course).