Re: Does automator really work - I cannot record more than 2 seconds
Re: Does automator really work - I cannot record more than 2 seconds
- Subject: Re: Does automator really work - I cannot record more than 2 seconds
- From: "John C. Welch" <email@hidden>
- Date: Thu, 19 May 2011 09:43:52 -0400
- Thread-topic: Does automator really work - I cannot record more than 2 seconds
Title: Re: Does automator really work - I cannot record more than 2 seconds
On May 19, 2011, at 8:51 AM, Gabriele Kahlout <email@hidden <mailto:email@hidden> > wrote:
On Thu, May 19, 2011 at 2:03 PM, John C. Welch < <mailto:email@hidden> email@hidden <mailto:email@hidden> > wrote:
On 5/19/11 2:25 AM, "Gabriele Kahlout" < <http://email@hidden> email@hidden <mailto:email@hidden> > wrote:
I'm not sure what's the different btw @ login and post-login, but let's say @ login is just fine. The ethernet cable is connected all the time.
Then
What a tricky question! I'm totally indifferent to whether it happens @ login or post-login
It’s not a “tricky question”, it’s a critically important one. If you want to log into your 802.1X network when you log into your machine, Automator is not able, physically or psychologically, to be of use to you, it cannot function outside of a user login context. If you want to log into your 802.1X network AFTER login, then you could in theory use Automator, but you’re going to be creating that workflow yourself. It would seem that logging into 802.1X at login is preferable, but hey, what would I know?
In any event, the root cause of your issue is FAR more a network configuration problem than it is an Automator problem and can be approached most efficiently from that angle. Or, you can keep flogging Automator, and eventually get it to work via GUI scripting or some such. Doesn’t matter to me, I don’t have the 802.1X problem that needs solving, you do.
I would recommend posting this question to the Mac OS X Server Admin list < <http://email@hidden> email@hidden <mailto:email@hidden> >. This is really less of an automator problem than a network configuration issue. I’m doing a bit of looking into it, but this problem something that the denizens of that list are more qualified to deal with.
the promise of automator is to automate manual workflows w/o scripting.
As long as someone else has created the workflows for you to use, that is indeed possible. If they have not, then you either have to create it yourself, or use a different method. It is a tool, not a magic wand, and like all tools, has limitations. It can't record processes that aren't recordable. It can't run workflows that don’t exist for it.
It’s up to you. You can accept that in this case, Automator is not the optimal tool for the task at hand, and that a different approach will be of more benefit for you, or, you can sit and demand a saw be able to hammer a nail. Do you want to solve the problem or do you want to fuss about with Automator?
--
John C. Welch Writer/Analyst
Bynkii.com Mac and other opinions
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Automator-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden