• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Using osacompile as non-root without window server running?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using osacompile as non-root without window server running?


  • Subject: Re: Using osacompile as non-root without window server running?
  • From: Axel Luttgens <email@hidden>
  • Date: Fri, 02 Jun 2006 23:30:32 +0200

On 26/05/06 10:27, Axel Luttgens wrote:
On 23/05/06 10:40, Pavel Janík wrote:
Hi,

is there any possibility to run osacompile as non-root user even without
window server running? E.g. when you are logged in remotely via ssh on your
Mac and no user is logged in on its console?
This doesn't seem to be currently possible (TN2083 may be of some relevance here).
For more information on this, please read

http://qa.openoffice.org/issues/show_bug.cgi?id=55642

Could you provide some contextual info about your precise problem, because you seem to face constraints but it is hard to tell which ones?
For example:
   - what is the role of the AppleScript in the project?
   - why compile on a remote box?
   - why don't you "want to build OO.org as root"?
   - could you adjust the sudoers file on the remote box?

Thanks for your answer.

Well, it seems you don't want to provide much feedback, and you thus don't help us to help you. ;-)

So, I had a look by myself and downloaded the whole OO thing; this has provided the answer to my first question: the AppleScript, in a sense, is... the whole application.
So, this rules out workarounds such as having the AppleScript being compiled at OO's first run time.

On the other hand, you don't seem to be a developer of OO.
In which case compiling on a remote host seems to be your own choice, not a constraint resulting of the need of a cooperative work; you thus presumably have full control on the remote host.
So, it seems that messing with the sudoers file on the remote box is the easiest way:
- devise a shell script that compiles the whole thing, checks everything, then changes the ownership/permissions to what you consider safe for the files resulting from the compilation,
- make sure that this script is writeable and executable by root only,
- edit the sudoers file so as to allow the execution of that very precise script, and only that script, with root permissions,
- execute the script on the remote host through ssh.
And you should be done; nothing spectacular, or?

Of course, I may be missing something.
But please then tell us what!

HTH,
Axel

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: Getting the path to root
  • Next by Date: Re: Getting the path to root
  • Previous by thread: Re: Getting the path to root
  • Next by thread: Current working directory...
  • Index(es):
    • Date
    • Thread