Jenkins slave defaults bugfix

[madAndroid]

This was causing an issue during slave process restart on CentOS7, resulting in the following:

[root@slave ~]# systemctl status jenkins-slave.service
jenkins-slave.service - SYSV: Jenkins Slave Swarm Client
   Loaded: loaded (/etc/rc.d/init.d/jenkins-slave)
   Active: failed (Result: exit-code) since Thu 2014-12-18 08:19:23 UTC; 1min 17s ago
  Process: 27562 ExecStop=/etc/rc.d/init.d/jenkins-slave stop (code=exited, status=0/SUCCESS)
  Process: 27569 ExecStart=/etc/rc.d/init.d/jenkins-slave start (code=exited, status=1/FAILURE)

Dec 18 08:19:23 slave.host systemd[1]: Starting SYSV: Jenkins Slave Swarm Client...
Dec 18 08:19:23 slave.host jenkins-slave[27569]: /etc/sysconfig/jenkins-slave: line 75: [-n: command not found
Dec 18 08:19:23 slave.host jenkins-slave[27569]: Starting Jenkins Slave...
Dec 18 08:19:23 slave.host systemd[1]: jenkins-slave.service: control process exited, code=exited status=1
Dec 18 08:19:23 slave.host systemd[1]: Failed to start SYSV: Jenkins Slave Swarm Client.
Dec 18 08:19:23 slave.host systemd[1]: Unit jenkins-slave.service entered failed state.

[jenkinsadmin]

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

[rtyler]

Weird, thanks for the fix