Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm following this tutorial, and I want to know the equivalent centos-version of this ubuntu-specific step:

You may receive a few warnings regarding fonts and such, but it’ll still work despite these. If you want the framebuffer to start automatically on system startup you can do:
sudo update-rc.d xvfb defaults 10

What's the proper way to start xvfb on startup on centos?

share|improve this question

4 Answers 4

up vote 11 down vote accepted

I use the following init script to add and start xvfb on boot just blat that in /etc/init.d/ and run chkconfig xvfb on

   #!/bin/bash
   #chkconfig: 345 95 50
   #description: Starts xvfb on display 99
   if [ -z "$1" ]; then
   echo "`basename $0` {start|stop}"
       exit
   fi

   case "$1" in
   start)
       /usr/bin/Xvfb :99 -screen 0 1280x1024x24 &
   ;;

   stop)
       killall Xvfb
   ;;
   esac
share|improve this answer
1  
dont forget add execute permission to this file: chmod +x xvfb –  panchicore Jan 21 '13 at 23:54
1  
Even though his question was posed for CentOS, it has become useful for other distributions, too. This works well on Ubuntu; you just need to run update-rc.d instead of chkconfig. See this answer for more information on update-rc.d. –  sigpwned Oct 18 '13 at 23:48

Here's a nice init script to accomplish this:

http://onemoretech.wordpress.com/2009/05/27/an-xvfb-init-script/

The script is:

#!/bin/bash
#
# /etc/rc.d/init.d/xvfbd
#
# chkconfig: 345 95 28
# description: Starts/Stops X Virtual Framebuffer server
# processname: Xvfb
#

. /etc/init.d/functions

[ "${NETWORKING}" = "no" ] && exit 0

PROG="/usr/X11R6/bin/Xvfb"
PROG_OPTIONS=":5 -screen 0 640x480x24"
PROG_OUTPUT="/tmp/Xvfb.out"

case "$1" in
    start)
        echo -n "Starting : X Virtual Frame Buffer "
        $PROG $PROG_OPTIONS>>$PROG_OUTPUT 2>&1 &
        disown -ar
        /bin/usleep 500000
        status Xvfb & >/dev/null && echo_success || echo_failure
        RETVAL=$?
        if [ $RETVAL -eq 0 ]; then
            /bin/touch /var/lock/subsys/Xvfb
            /sbin/pidof -o  %PPID -x Xvfb > /var/run/Xvfb.pid
        fi
        echo
        ;;
    stop)
        echo -n "Shutting down : X Virtual Frame Buffer"
        killproc $PROG
        RETVAL=$?
        [ $RETVAL -eq 0 ] && /bin/rm -f /var/lock/subsys/Xvfb
 /var/run/Xvfb.pid
        echo
        ;;
    restart|reload)
        $0 stop
        $0 start
        RETVAL=$?
        ;;
    status)
        status Xvfb
        RETVAL=$?
        ;;
    *)
     echo $"Usage: $0 (start|stop|restart|reload|status)"
     exit 1
esac

exit $RETVAL

Save the script as xvfbd and copy the script to /etc/init.d, then run the following command:

sudo chkconfig --add xvfbd
share|improve this answer

And now, the systemd answer.

It has been almost four years since these questions and answers, and the world has changed whilst they have not. Since version 7, CentOS has used systemd. Ubuntu is mentioned in the question and in comments. Since version 15, Ubuntu has used systemd too.

Although one can use System 5 rc scripts under systemd, the scripts in answers here are highly suboptimal, to say the least. One blithely uses killall, whose problems for dæmon management are well known; and the other is a mess of rickety lock file and PID file logic none of which is actually necessary under a service manager, since service managers themselves keep track of dæmon processes.

As I have said elsewhere, if you're starting to learn this stuff and are on CentOS Linux version 7 or later or Ubuntu Linux version 15 or later, don't begin with System 5 rc scripts in the first place. Begin with systemd unit files.

a template for multiple Xvfb services

Simple xvfb.service systemd unit files for xvfb can be found at Adding Xvfb to systemd services and at http://askubuntu.com/a/621256/43344 . However, as I mentioned at the latter one can also take a templatized approach:

[Unit]
Description=virtual frame buffer X server for display %I
After=network.target

[Service]
ExecStart=/usr/bin/Xvfb %I -screen 0 1280x1024x24

[Install]
WantedBy=multi-user.target

As a locally-written, non-system non-packaged, unit file for system-wide (as opposed to per-user) services this goes into /etc/systemd/system/xvfb@.service of course.

controlling the services

One instantiates the template, into an actual named service, with the display number that is desired. For display :99, therefore, there is an actual service instance named xvfb@:99.service.

  • Set the service to auto-start on bootstrap with systemctl enable xvfb@:99.service .
  • Unset auto-starting the service with systemctl disable xvfb@:99.service .
  • Start the service manually with systemctl start xvfb@:99.service .
  • Stop the service manually with systemctl stop xvfb@:99.service .
  • Inspect the current service status in detail with systemctl status xvfb@:99.service .

Further reading

share|improve this answer

You can use a more easier way if you just need to start or launch something on the computer boot. On Redhat/CentOS, add your script line on this file :

/etc/rc.d/rc.local

I hope it will help you :)

share|improve this answer
    
I did not downvote you, but I think this only worked for System V. –  Donato Jun 6 at 14:35

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.