Saturday, September 28, 2013

Fedora yum install Chromium



Chromium web browser

Fedora does not include Chromium web browser in the official repository due to problems outlined in
Tom 'spot' Callaway, Manager of the Fedora Engineering team at Red Hat is working with Google to fix the problems in Chromium so that it can be made available in the official repository. He also maintains his own test packages of Chromium

Stable repository

To use this repo, download the repo file from from http://repos.fedorapeople.org/repos/spot/chromium-stable/fedora-chromium-stable.repo and drop it in /etc/yum.repos.d as root user or run the following command
sudo yum-config-manager --add-repo=http://repos.fedorapeople.org/repos/spot/chromium-stable/fedora-chromium-stable.repo
Use PackageKit or run the following command
sudo yum install chromium -y

Posted by at No comments:
Labels: ,

Thursday, September 26, 2013

Installing remmina on Fedora 19 



yum search remmina-plugin
yum install remmina-plugins-rdp
yum install remmina-plugins-vnc


http://blogdaprima.com/2011/installing-remmina-on-fedora-15-to-connect-remotely-windows-servers/
Posted by at No comments:
Labels: , ,

Monday, September 23, 2013

Fedora 19 MATE - emerald-themes , Desktop Cube Effects with compiz



Compiz effects doesn't work in Gnome Shell and Cinnamon desktops.
http://www.server-world.info/en/note?os=Fedora_19&p=x&f=3
yum -y groupinstall "Cinnamon Desktop"
echo "exec /usr/bin/gnome-session-cinnamon" >> ~/.xinitrc
startx

 http://www.server-world.info/en/note?os=Fedora_19&p=x&f=4
yum -y groupinstall "MATE Desktop" 
echo "exec /usr/bin/mate-session" >> ~/.xinitrc
startx

http://www.zealfortechnology.com/2013/07/install-mate-desktop-compiz-fedora-19.html
sudo yum install compiz compiz-mate fusion-icon
sudo yum install compiz-plugins-main compiz-plugins-extra compiz-plugins-unsupported emerald-themes emerald-themes-extra
gsettings set org.mate.session.required-components windowmanager compiz-mate-emerald
http://www.makeuseof.com/tag/gnome-based-desktop-environments-explained-mate-vs-gnome-shell-vs-unity-vs-cinnamon/

 MATE is the continuation of Gnome 2, so if you’ve used Gnome 2 (or are still using a very old distribution to keep it), then MATE will seem extremely familiar. There may be a few applications with different names (Nautilus is called Nemo in MATE), but otherwise everything should be the same. The use of GTK3 is minimal if at all, so you won’t be able to benefit from any of those advancements. But it’s a great desktop environment if you were completely happy with the way things were and just want continued bug fixes.
If you want to take advantage of the Gnome 3/GTK3 backbone without having to deal with Gnome Shell or Unity, then your best choice is Cinnamon. For a handful of people who still want to stay in the Gnome track and yet use the latest software, this may be their best choice. It lets people still use GTK3 themes as well as Gnome 3′s Control Center, but the desktop is very similar to that of Windows/KDE in that there is a single panel along the bottom of the screen, and a Start Menu-like button at the bottom left corner.
The Cinnamon project was created by the team behind Linux Mint, continuing their mission to fix what they believe are usability issues in Ubuntu. While Cinnamon is the default desktop environment for Linux Mint (with MATE available as well), both Cinnamon and MATE should be available for a large number of other distributions.
Posted by at No comments:
Labels: , ,

Thursday, September 5, 2013

FEDORA systemctl start rc-local



Auto running commands at boot


 

Create the rc.local file in the /etc/rc.d directory, 
and make sure the first line is #!/bin/sh


 /etc/rc.d/rc.local file also can start at the top with:

#!/bin/bash


Then activate this service with something like:
# systemctl enable rc-local.service


Make the rc.local file executable
# chmod 700 /etc/rc.d/rc.local


 If there's problems : 
cat /var/log/messages | grep rc.local 

/etc/rc.d/rc.local is the place for the commands but you have to ensure the
rc-local service is enabled and running.
[root@gate depit]# 
[root@gate depit]# service rc-local status
Redirecting to /bin/systemctl status  rc-local.service
rc-local.service - /etc/rc.d/rc.local Compatibility
   Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static)
   Active: failed (Result: exit-code) since Wed 2013-11-27 23:22:57 EET; 42min ago
[root@gate depit]# 

 /etc/rc.local does not get executed on sytem bootup
https://bugzilla.redhat.com/show_bug.cgi?id=843735
fedora systemd service "rc-local" ExecStart "code=exited" "status=7"

 
Description of problem:
/etc/rc.local is the script within whihc if any commands are found should get executed on bootup, but is not happening on Fedora 19


I am using Network-Manager. network daemon is switched off & ethernet interfaces are managed by NM only.






I think this will work for you if you do 'systemctl enable NetworkManager-wait-online.service'.

Getting Fedora 18, 19  to start the service can be done as root:
# systemctl start rc-local
# systemctl status rc-local



How to disable screen blanking on text console : 
if setterm command is put on rc.local , then it has no effect :
setterm -blank -0 
instead , add setterm -blank X (X in minutes, 0 to disable) to a shell init file like .bashrc.
after login , 
cat /sys/module/kernel/parameters/consoleblank 


returns 0 


http://unix.stackexchange.com/questions/8056/disable-screen-blanking-on-text-console


http://superuser.com/questions/152347/change-linux-console-screen-blanking-behavior
















Posted by



at





No comments:
  






















Labels:

























named chroot on Fedora 18














systemctl stop      named.service

systemctl disable named.service

systemctl enable  named-chroot.service

systemctl start     named-chroot.service




















Posted by



at





No comments:
  






















Labels:
,

























vsftpd selinux fedora 18












getsebool -a | grep ftp

ftp_home_dir --> off

ftpd_anon_write --> off

ftpd_connect_all_unreserved --> off

ftpd_connect_db --> off

ftpd_full_access --> off

ftpd_use_cifs --> off

ftpd_use_fusefs --> off

ftpd_use_nfs --> off

ftpd_use_passive_mode --> off

httpd_can_connect_ftp --> off

httpd_enable_ftp_server --> off

sftpd_anon_write --> off

sftpd_enable_homedirs --> off

sftpd_full_access --> off

sftpd_write_ssh_home --> off

tftp_anon_write --> off

tftp_home_dir --> off







 setsebool ftp_home_dir on








setsebool -P ftp_home_dir 1 
to make it permanent









getsebool -a | grep ftp



ftp_home_dir --> on



ftpd_anon_write --> off



ftpd_connect_all_unreserved --> off



ftpd_connect_db --> off



ftpd_full_access --> off



ftpd_use_cifs --> off



ftpd_use_fusefs --> off



ftpd_use_nfs --> off



ftpd_use_passive_mode --> off



httpd_can_connect_ftp --> off



httpd_enable_ftp_server --> off



sftpd_anon_write --> off



sftpd_enable_homedirs --> off



sftpd_full_access --> off



sftpd_write_ssh_home --> off



tftp_anon_write --> off



tftp_home_dir --> off









ERROR : 

500 OOPS: vsftpd: refusing to run with writable root inside chroot ()



SOLUTION : 

vi /etc/vsftpd.conf and add the following
allow_writeable_chroot=YES




















Posted by



at





No comments:
  






















Labels:
,

















          

        

          

        

Tuesday, July 16, 2013


          

        









MAIL EXPN VRFY ETRN
















sendmail ERROR "did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA"



We had to investigate problems relaying mail from a certain IP. Looking through the MTA logs, we see:



Jul 16 15:40:29 gate sendmail[30309]: r6GCcjKJ030309:
          spamfilter2.starnet.md [178.168.2.134] did not issue
          MAIL/EXPN/VRFY/ETRN during connection to MTA

        Jul 16 15:57:11 gate sendmail[30913]: r6GCtSW0030913:
          spamfilter2.starnet.md [178.168.2.134] did not issue
          MAIL/EXPN/VRFY/ETRN during connection to MTA

        Jul 16 16:17:12 gate sendmail[31567]: r6GDFTme031567:
          spamfilter2.starnet.md [178.168.2.134] did not issue
          MAIL/EXPN/VRFY/ETRN during connection to MTA
Jul 16 16:18:16 gate sendmail[31617]: r6GDGVie031617:
          smtpclu-6.eunet.rs [194.247.192.231] did not issue
          MAIL/EXPN/VRFY/ETRN during connection to MTA

        Jul 16 16:22:57 gate sendmail[31786]: r6GDLEbe031786:
          smtpclu-6.eunet.rs [194.247.192.231] did not issue
          MAIL/EXPN/VRFY/ETRN during connection to MTA

        Jul 16 16:50:59 gate sendmail[32740]: r6GDnIa1032740:
          smtpclu-6.eunet.rs [194.247.192.231] did not issue
          MAIL/EXPN/VRFY/ETRN during connection to MTA

        Jul 16 17:22:54 gate sendmail[1672] : r6GEL9oM001672:
          smtpclu-6.eunet.rs [194.247.192.231] did not issue
          MAIL/EXPN/VRFY/ETRN during connection to MTA




On the other side , the error eMaiL was : 






Reporting-MTA: dns; spamfilter.starnet.md
Arrival-Date: Tue,  9 Jul 2013 22:03:38 +0300 (EEST)

Final-Recipient: rfc822; dircom@mydomain.com
Action: failed
Status: 4.0.0
Diagnostic-Code: X-Spam-&-Virus-Firewall; connect to
    [27.10.97.70]: read timeout







A Cisco PIX between the host and our mail relay is performing SMTP inspection ("SMTP Fixup"). 




The sending MTA apparently does not know how to handle a "500 5.5.1" response from our MTA, and keeps the connection open for one hour (default Timeout.command in sendmail). After one hour, our MTA closes the connection.




As a workaround, enable ESMTP inspection, or disable SMTP inspection. ESMTP inspection allows commands described in RFC 2821. Note that ESMTP inspection and SMTP inspection are mutually exclusive.



http://brandonhutchinson.com/wiki/SMTP_Fixup_problems

http://www.cisco.com/en/US/products/sw/secursw/ps1018/products_configuration_example09186a008064730a.shtml







http://frustratedtech.com/post/41281442135/sendmail-dropping-connections-from-monitoring-servers

http://www.sendmail.com/sm/open_source/docs/configuration_readme/









 Sendmail Dropping Connections From Monitoring Servers?




I’ve been seeing this frequently.  We currently use IPMonitor at work. 
 I hate it.  But, it is what it is, gotta use what is provided.  So, 
this monitoring system uses snmp to check all services and then it also 
tries to connect to smtp.  However, one server is setup to require pop3 
login before smtp access can be acquired.  This was giving plenty of 
false positives for the monitoring system since we were seeing this 
message a lot.


# tail -f /var/log/maillog


Jan 23 04:02:02 LUX5 sendmail[8278]: r0N922sj008278: [123.456.789.10] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA




To fix this I needed to add the monitoring server to the access file for sendmail to accept the connection.


# nano /etc/mail/access


# Check the /usr/share/doc/sendmail/README.cf file for a description
# of the format of this file. (search for access_db in that file)
# The /usr/share/doc/sendmail/README.cf is part of the sendmail-doc
# package.
#
# by default we allow relaying from localhost...
connect:localhost.localdomain           RELAY
connect:localhost                       RELAY
connect:127.0.0.1                       RELAY
######ADD YOUR IP BELOW#########
connect:123.456.789.10                  OK




Then
 just rebuild the database and restart sendmail. You will see see the 
error message, but at least you will no longer get the false positives.


# makemap hash /etc/mail/access < /etc/mail/access


# service sendmail restart














Posted by



at





No comments:
  






















Labels:
,

















        

      









Subscribe to:
Posts (Atom)