FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Restart a service after updating config file

Restart a service after updating config file 30 Aug 2016 13:03 #2365

  • Jonas Bygden
  • Jonas Bygden's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 11
  • Thank you received: 0
Is there an easy way to restart a service (in my case syslogd) after updating its config file via Filewave?

Restart a service after updating config file 09 Sep 2016 14:21 #2368

  • Hans-Joachim Adermann
  • Hans-Joachim Adermann's Avatar
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 11
  • Karma: 1
  • Thank you received: 0
this might work

launchctl unload /System/Library/LaunchDaemons/com.apple.syslogd.plist; do_what you_want; launchctl load /System/Library/LaunchDaemons/com.apple.syslogd.plist


Restart a service after updating config file 12 Sep 2016 08:39 #2370

  • Jonas Bygden
  • Jonas Bygden's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 11
  • Thank you received: 0
Well, yes, since that's the way I did it on my test-workstation. My question wasn't really how to restart syslogd in OS X, but rather how to do it using FileWave. Is it just to put these commands in a script and "push" that to all clients, or is there a better way?

Restart a service after updating config file 19 Oct 2016 19:14 #2388

  • Tyler Myers
  • Tyler Myers's Avatar
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 5
  • Thank you received: 1
Putting commands in a simple script and pushing to clients does seem to be the best way.

Restart a service after updating config file 01 Nov 2016 13:18 #2405

  • Jonas Bygden
  • Jonas Bygden's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 11
  • Thank you received: 0

myerstk wrote: Putting commands in a simple script and pushing to clients does seem to be the best way.

Yes, that's what I thought as well. However being rather new with Filewave I'm wondering how I execute that script on the clients, or rather how to make sure that it's run after being distributed.

Restart a service after updating config file 01 Nov 2016 13:30 #2406

  • Tyler Myers
  • Tyler Myers's Avatar
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 5
  • Thank you received: 1
Toss your script into a blank fileset. I Usually put mine in /usr/local/scripts/. Drill down into your fileset select the the script and do a get info. Click over to the executables tab, there you can set it to execute once upon activation. Filewave will execute it once at the root level. To see if its run properly you can do a few things. You can have your script write to a log with any errors to check for troubleshooting. You can also select the fileset and hit report. That will show the live status of each client that has that fileset associated. From the report screen you can tell the script to execute again if you need it.

Hope this helps.
The following user(s) said Thank You: Jonas Bygden

Restart a service after updating config file 24 Nov 2016 08:55 #2421

  • Mikael Sigemo
  • Mikael Sigemo's Avatar
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 2
  • Thank you received: 0
In the later versions of FileWave you got some more settings to edit when it comes to script.

You can now toss the script in the same fileset as the configfile.
Just follow myerstk "how-to" but put the script in the same fileset.
In Fileset view select the fileset and hit the "Script" button. In the settings window opened you cad set when the script shall run. The default value is "Activation"
Attachments:
  • Page:
  • 1