Cron job reasoning - use a plist instead? about dynamic_walls HOT 12 CLOSED

Ok, all done. Give this a try on your machine and let me know how it works. You should be able to unzip, double click and let it go. It's only zipped because GitHub doesn't allow .command files.
Plist Generator.zip

from dynamic_walls.

So, I renamed your script to wallpaper.plist edited the username inside and placed it in /Library/LaunchDaemons/ changed the owner to root and restarted. After entering: "launchctl load /Library/LaunchDaemons/wallpaper.plist" it finally worked.

from dynamic_walls.

Yes, I should've been more specific with my instructions. What you did is correct, you can also use launchctl unload ... to disable it.

from dynamic_walls.

The only problem is that the wallpaper files a from my user account and when I place your plist inside /Library/LaunchDaeomons/ it won't work, but if I place them inside/User/Username/Library/LaunchAgents your script works just fine.

from dynamic_walls.

@john2691 my main purpose was to create the main script and suggested a cron job as it was simple to set up even for someone a little new to all of this, I did suggest using a plist and launchd just above the P.S for those who know what they are doing, launchd is definitely the better option and replaces cron, just thought using cron would be easier but we could move to a plist that is better, I'm not too familiar with those I did try it out earlier when I was building it, is there a way to set a universal plist so the user doesn't have to specify the absolute path?

I would like to use the plist method too

from dynamic_walls.

@Dniel97, that's certainly strange, it runs on my machine without issue. I'll have to look into it. @kush-agra so long as they're putting the files in the /Pictures/Wallpapers folder, I think ~/Pictures/Wallpapers should suffice in the .plist file. I can experiment with it.

from dynamic_walls.

@john2691 It works just fine in /Users/USERNAME/Library/LaunchAgents, but I don't know why it isn't working in /Library/LaunchDaemons/

from dynamic_walls.

oh nice, surely let me know @john2691 after experimenting and I'll set it up for a plist instead that'd be great

from dynamic_walls.

@kush-agra It looks as though the absolute path is required, since it's an AppleScript and not a shell script. Shell scripts are able to be called in a plist using the ./ method, but not AppleScripts. I'll try to think of an elegant way to make that easy for users, but so long as cron isn't causing issues it's not that important.

from dynamic_walls.

exactly my thought process, we could use a shell script to call the AppleScript?

from dynamic_walls.

That's one solution, I'm actually writing a script right now that will get the current username, create a proper .plist file and put it in the correct folder. Either way should be pretty user friendly.

from dynamic_walls.

Seems to be working great and is easier, I'll add it to master :)

from dynamic_walls.