Welcome to my website. I am always posting links to photo albums, art, technology and other creations. Everything that you will see on my numerous personal sites is powered by the formVistaTM Website Management Engine.

icon.linkedin.jpgicon.twitter.jpg

  • [SOLVED] Unable to Customize Keyboard Shortcuts for Switching Between More Than 4 Workspaces in GNOME on CentOS 7 or RHEL 7
    08/22/2017 6:02PM
    I am working on a VM that is running GNOME under RHEL 7 and I typically run with 12 workspaces.  The default GNOME install only has the keyboard shortcut configurations up to "Switch to workspace 4".

    It turns out that the solutions is to use the gsettings cli tool to add additional shorcuts.

    $ gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-5 "[\"<Control>F5\"]"
    $ gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-5 "[\"<Alt>5\"]"
  • Services That Can Be Turned Off in a CentOS 6, Minimal Server
    08/22/2013 9:14PM

    Following is a list of services that can (for most applications) be turned off if you are setting up a bare-bones CentOS 6.4 server:

    Automatic bug reporting services:
    abrt-ccpp
    abrt-oops
    abrtd

    Power control and features, query battery and config status
    acpid

    Controls 'at' command queing, examining, or deleting jobs for later execution.  Anything atd can do, cron can do
    atd

    File auditing
    auditd

    Auto fs mounting
    autofs

    Printing
    cups

    For desktop environments:
    netfs

    Network filesystems:
    nfslock
    rpcbind
    rpcgssd
    rpcidmapd

    MTA
    postfix

    ip6tables

    Sends anonymized usage stats:
    udev-post

  • Configuring JBoss 6.x to Run as a Service Under RHEL and CentOS
    12/22/2011 11:28AM

    In most cases you will want to run JBoss as a non-privileged user.  For this example we will set up a jboss user (adding the user is an excersize for the user).  This example covers jboss-6.1.0-Final.

    • Add $JAVA_HOME and $JBOSS_HOME environmental vars to .bash_profile for your jboss user.  $JAVA_HOME points to your install of the JDK and $JBOSS_HOME points to your jboss installation directory.
      JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk.x86_64
      export JAVA_HOME
      PATH=$JAVA_HOME/bin:$PATH
      export PATH
    JBOSS_HOME=/opt/jboss/
    export JBOSS_HOME

    • Once you have done the basic JBoss installation set up, copy the jboss_init_redhat.sh to /etc/init.d/jboss.
    • Add the following directly below the #!/bin/bash line:
    # description: JBoss Start Stop Restart
    # processname: jboss
    # chkconfig: 234 20 80

    • Set JBOSS_HOME
    • JAVAPTH to the location of your JDK
    • Set JBOSS_CONF to the profile you want to run
    • define a $JBOSS_HOST variable and set it to either the IP address or host name of the machine on which you are running jboss.
    • Update the JBOSSCP to include the jbossall-client.jar
    JBOSSCP=${JBOSSCP:-"$JBOSS_HOME/bin/shutdown.jar:$JBOSS_HOME/client/jbossall-client.jar"}
    • Replace the JBOSS_CMD_STOP with the following line (the uid:password combo is whatever you used to lock down the admin console in jboss):
    JBOSS_CMD_STOP="$JBOSS_HOME/bin/shutdown.sh -s service:jmx:rmi:///jndi/rmi://192.168.126.128:1090/jmxrmi -u admin -p password"
    • Enable jboss as a service in the OS:
    • Make the jboss script executable:
    • # chmod 755 jboss
    Add it as a service via chkconfig:
    • # chkconfig --add jboss
    Set the run levels for the jboss service
    • # chkconfig --level 2345 jboss on
  • Fix For: Pango-WARNING **: failed to choose a font, expect ugly output and Other FireFox Errors
    11/29/2011 1:54PM
    $ firefox &
    [1] 1933

    $
    (firefox:1947): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'
    GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -? 1: Failed to get connection to session: /bin/dbus-launch terminated abnormally without any error message)

    (firefox:1947): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'
    GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -? 1: Failed to get connection to session: /bin/dbus-launch terminated abnormally without any error message)
    /usr/lib64/firefox-3.6/run-mozilla.sh: line 131:? 1947 Segmentation fault????? "$prog" ${1+"$@"}

    [1]+? Exit 139??????????????? firefox


    Should you see such an error when attempting to run FireFox from a remote terminal connecting to a local XServer (Xming, or similar) check the following:

    1. That the haldaemon is running
    2. That the dbus-x11 package is installed.? On RedHat based systems, you can yum install dbus-x11
    3. That you have fonts installed.? I did a bit of a brute force approach and ran: yum groupinstall 'Fonts'
  • Configuring CentOS to run SELinux in Strict Mode
    08/29/2011 5:05PM

    I am in the process of setting up some CentOS/RHEL 6 servers to run SELinux in strict mode.? What follows are notes, links to online resources and things that I am discovering along the way.? Once I am finished I will go back and re-write it to follow more of a how-to/guide type format.? In the meantime, it might seem a bit disjointed.

    Links/Resources:

    • http://wiki.centos.org/HowTos/SELinux
    • http://fedoraproject.org/wiki/SELinux
    • http://www.centos.org/docs/5/html/Deployment_Guide-en-US/rhlcommon-chapter-0001.html
    • http://www.nsa.gov/research/selinux/index.shtml

    MaintLog Notes:

    • Make sure that the selinux-policy-strict package (and deps) are installed:
    • # yum install selinux-policy-strict
    • After installing the policy I was unable to reboot as I hadn't relabeled the file system properly.? If having problems booting try:
    • # genhomedircon
    • # touch /.autorelabel
    • # reboot
    • After successfully booting with strict mode enabled you will not be able to do the things that you would normally expect as a root user.?This is because your root shell does not have access to the system administrator role.? To do so invoke the newrole command:
    • # newrole -r sysadmin_r
    • LEFTOFF: it seems semanage isn't installed.? I'll need to restart with selinux disabled to install it so that I can sort out running newrole properly:? see: http://www.spinics.net/lists/selinux/msg09681.html
    • Make sure that the semanage package is installed: # yum install libsemanage


  • 1 2 >>
Advanced Search

Categories

Archives