Skip to main content

Posts

Showing posts with the label Fedora

Plone installation in Fedora Linux

This document will help you to install and configure Plone in Fedora Linux. (I think you can use this same steps to install Plone in CentOS and Redhat Enterprise Linux.)   Make sure you have Fedora repositories enabled. (Here I'm using "dnf" command.  If you are using CentOS, Redhat or Older versions of Fedora then you have to use "yum" command instead ) $ sudo dnf repolist Last metadata expiration check: 0:07:08 ago on Sun Jul 9 01:18:52 2017. repo id repo name status *fedora Fedora 25 - x86_64 51,669 *updates Fedora 25 - x86_64 - Updates 20,457 Now you have to install the per-requesites for Plone. (You have to install it manually)   $ sudo dnf install libxml2-devel libxslt-devel \ libjpeg-turbo libjpeg-turbo-utils libjpeg-turbo-devel \ zlib zlib-devel perl-Compress-Raw-Zlib perl-IO-Zlib 1. Now you can download ...

rtl8723be driver issues in Fedora, Ubuntu, CentOS and Redhat Linux (RHEL).

I could see many people bug the developer with silly questions... I faced this issue on both Ubuntu, CentOS, and Fedora.  What I found is, the driver which Ubuntu, CentOS, or Fedora shipped is the latest one. There is no need of downloading and compiling the drivers again, without testing the installed driver with different antenna selections. In most cases re-enabling the kernel module with correct antenna selection would help.  (I think it will work in Redhat as well. But not tested.) Let me share my finding... To fix this you have to unload the current kernel modules and then insert them again with the new antenna selection... In my case, In Ubuntu the antenna was 2,  in centOS7 and Fedora, it was 1. So here are the steps (which I did). In UBUNTU (16.10, 17.04) ## Unload the current module ## sudo modprobe -rv rtl8723be ## Reload it with new option. ## sudo modprobe -v rtl8723be ant_sel=2 ## this step will help you to keep the same changes even after the...

/var/log/lastlog is very big in size.

My backup team reported that the backups are failed. And on investigation I found /var/log/lastlog is very huge in size but file system usage is normal in "df" output.  And even "du" command also shows normal in size. I found this information from redhat. This file is what we call a sparse file. A sparse file is a file that contains unallocated blocks or "empty space", as it implies, it does not actually take up filesystem space. To test this theory, execute the following command: root@server1.nyc.us:/var/log # ls -l /var/log/lastlog -rw-r--r-- 1 root tty 459561084068 Jul 1 13:05 /var/log/lastlog root@server1.nyc.us:/var/log # du -sh /var/log/lastlog 23M /var/log/lastlog See the ls -l output, which shows huge size. The fix which they have suggested is to copy/move the file to some other place, because the copying will clear the unallocated blocks. But I found the copy is taking more time. So I decided to to clear the file after stopping th...