Re: How to run a command for a Mac client

2010-10-08 Thread Minns, Farren - Chichester
Aha, ok the the simplets solution is the best :-) Works a treat. Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Remco Post Sent: 07 October 2010 18:08 To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] How to run a command for

Re: How to run a command for a Mac client

2010-10-08 Thread Guido Martínez
El oct 8, 2010 4:58 a.m., Minns, Farren - Chichester fmi...@wiley.com escribió: Aha, ok the the simplets solution is the best :-) Works a treat. Thanks Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf ... Have you considered creating

How to run a command for a Mac client

2010-10-07 Thread Minns, Farren - Chichester
Hi all, I wonder if you can help. I need to schedule a Mac client to do a daily incrbydate backup. On the client I have created a file called daily-incrbydate.sh with the single line dsmc incremental -incrbydate in. If I run this directly it works fine, but when I try to create a schedule on

Re: How to run a command for a Mac client

2010-10-07 Thread Richard Sims
Did you follow the quoting specifications documented for the DEFine SCHedule command, to deal with the blank characters in the string?

Re: How to run a command for a Mac client

2010-10-07 Thread Minns, Farren - Chichester
Hi Richard I was just using double quotes, so now use single and double. The schedule looks as follows and still fails with ANR2579E Schedule MACSERVERS in domain STANDARD for node CHI-XS02 failed (return code 127). Policy Domain Name: STANDARD Schedule Name: MACSERVERS

Re: How to run a command for a Mac client

2010-10-07 Thread Richard Sims
Hi, Farren - Making progress... The 127 error is complaining about the path of the command. I don't see that you need the /Server HD at the front of the path spec: have it start with /Applications and give that a try, first doing 'ls -l' on the revised path to verify the file path, and assure

Re: How to run a command for a Mac client

2010-10-07 Thread Minns, Farren - Chichester
Wonderful, that seems to be working :-) Thank you. One final question though. Can I run this command such that I still see the output as I would in the normal dsmsched.log? Regards Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of

Re: How to run a command for a Mac client

2010-10-07 Thread PAC Brion Arnaud
Farren, Try to add /some_path/log_file_name at the end of your command. Also, make sure that there is no quiet commutator in your dsm.opt file, or replace it with verbose. Cheers. Arnaud ** Corporate IT Systems

Re: How to run a command for a Mac client

2010-10-07 Thread Minns, Farren - Chichester
Wonderful, works a treat. Thanks to all for the help. Regards Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of PAC Brion Arnaud Sent: 07 October 2010 14:49 To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] How to run a command for a Mac

Re: How to run a command for a Mac client

2010-10-07 Thread Remco Post
Have you considered creating a normal Incremental schedule and using -opt='-incrbydate' flag? This seems to be far less error prone? On 7 okt 2010, at 13:56, Minns, Farren - Chichester wrote: Hi all, I wonder if you can help. I need to schedule a Mac client to do a daily incrbydate