-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sanjay Upadhyay wrote:
| yes, it would be very helpfull, at present many such | tasks are required, which are being done manually I looked into this some more. It's works a little differently than I initially thought. The registry paths are used to detect the presence of the task scheduling agent on the remote host. The actual jobs are simply stored as files. In my mind this would fit pretty well as just a ~/cron directory for a given user. For example, it I run a job as jerry, then the job script would be stored in ~jerry/cron and a crontab entry would be made in /var/spool/cron/jerry. I'm still thinking this over. The other detail is to figure out the file format used to present the job properties dialog to Windows. This is probably already decoded somewhere (similar to *lnk files or something). cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC3PtMIR7qMdg1EfYRAkYPAKCKa/c21fGnIWFs7BrxPSIxpVycuwCgg/mL 9WhVJspA0omyohwarFoV7jc= =o686 -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
