Create Unix Executable file

Hi Folks,
I've got a simple terminal command...hamachi start...that I would like to run as LaunchAgent plist file or as an executable file triggered by a LaunchAgent.
For the former I currently have:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.HamachiLogin</string>
<key>ProgramArguments</key>
<array>
<string>hamachi start</string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
But it doesn't work, so I thought I'd make an executable file containing the command and put that in the <string> section above.
Anyone with any thoughts?
Thanks!
TP

Your .plist likely doesn't work because your <ProgramArguments</> is invalid.
For a start, every element of the command needs to be specified as a separate entity. This includes the command itself, plus any parameters.
In addition to that, you need to be specific about the location of such scripts. You cannot assume that the OS will find the script, so you should always specify the full path to the command.
Therefore your command should look more like:
<key>ProgramArguments</key>
<array>
<string>/usr/local/bin/hamachi</string>
<string>start</string>
</array>

Similar Messages

Word Docs have become Unix Executable Files!

The subject says it. This has happened on both my wife's iMac G5, and my MacBook Pro. Some, not all, of our Word docs, (both using 2004, running OS X.4.7) have had their icons turned into a gray console, and in "Get Info" identify themselves as "Unix Executable File." When opened in Word, I get the option to open as if it were a foreign file, and typically, it opens with all formatting gone, and all kinds of bizarre characters at the beginning (and sometimes end) of the doc.
Now, I can salvage the data, it seems, but is there some way to simply undo this damage without manually going through every file?
I must say, this is exactly the kind of junk that I would expect to find on a PC. This is a stunningly bad problem, by far the worst I've experienced in almost 15 years of using Macs. I would assume that Apple is aware of this, and that they can:
1) Explain what happened.
2) Explain a quick and easy fix.
Thanks to anyone (from Apple or otherwise) who can do 1 and 2 above.

Jeffois,
The first command I gave to you will render the directory in question, and all nested directories, inaccessible. The second command will make the diretories accessible again.
There is a possibility that there are files in this directory structure which are not owned by you. Not likely, but I must make the assumption that these could be encountered when I give such commands "in the dark" as it were. In such a case, you would see an error regarding these files, thus the warning.
You can return your directories to accessibility using the second command, regardless of errors you might encounter. If you do encounter errors, I will post a different form of the same commands that will work.
Be prepared to deal with this problem any time you transfer files from a Windows-formatted volume. This is not a Windows problem, but rather one of differences between the two file systems. If you see a file show up with the executable icon, you might want to remove the execute bit right away. Unfortunately, there is no way to do this in the GUI, so you must resort to using Terminal.
This shouldn't be too much of a problem. Just open Terminal, type this text with a traling space:
<pre style="overflow:auto; font-family: 'Monaco'; font-size: 10px">chmod a-x</pre>
then select all of the new files and drag them all into the Terminal window. This will create a rather long command line that includes the full path to every file you dragged in. Just press <RETURN>, and "POOF," no more execute bit!
Scott

Photoshop .psd files converted to Unix Executable files

I'm an illustrator and I store my art on CDs and DVDs. After a period of time my files are converted from Photoshop .psd files to Unix Executable files and I can't open them. What can I do to get my work back??? -and keep this from happening in the future. Why does it do this????
Thanks for any help.

The file sizes range from 22.2 MB to 67.9 MB.
Size isn't the issue then. Linc was asking that question because we see that with other file types. Older fonts in particular, which have all of their data in the resource fork. If that gets stripped, you end up with a zero byte file.
Does that mean I'll have to go through the Adobe authorization process for Photoshop again?
If the version of Photoshop you're currently using is already activated, then no. Either way, it has nothing to do with .psd files showing as UNIX executables.
In Windows, any file that doesn't have an association to a program is displayed as a white, dog-eared piece of paper with the Windows logo in the middle. That's Windows' way of saying, "I have no idea what this is." In OS X, (except for those files which actually are UNIX executables), displaying them as such is OS X's way of saying the same thing.
I thought I was home free when the icon changed to a thumbnail picture of the illustration, but PS refuses to open it saying it is not a Photoshop file. ???
Now that is weird. As of Snow Leopard, Apple put the old Type and Creator codes to rest. It will read them as a last resort to try and identify an older file, but none of Apple's applications add them to any file they save. For better compatibility with Windows, and OS X's own underlying UNIX core, file extensions have taken their place. So adding a .psd extension should have worked. Without playing with one of your files, I couldn't tell you why Photoshop declared it wasn't a valid .psd image.
On a side note, Apple added Uniform Type Identifiers to OS X to keep things separate. A big problem in Windows is that multiple apps may use the same file extension. EPS is a big one in printing. So you have Photoshop, Illustrator, Freehand, Quark and others all using .eps for Encapsulated PostScript files. However, Windows can only associate one application to any given extension. So if Illustrator happens to be the one tagged to .eps files, it will try to open any file ending in .eps, no matter what program actually created it. OS X keeps them separate with Uniform Type Identifiers. So even though multiple files may have .eps file extensions, the extra metadata keeps track of what program it actually belongs to.
This is what is part of the LaunchServices database, and was why it was my first suggestion. If that database is wonky, you'll see weird things like this. Have you tried clearing it yet?
The files are fine when newly burned to CD. It is only months, or years, later that they become Unix Executable Files. This has happened to just about all of my CD backups and it's frustrating to think that CD backup doesn't work across newer OSs and Photoshop upgrades. I suspect that may be the problem, but it just shouldn't happen.
That shouldn't make a difference. I've got a bunch of very old files created in Photoshop back from OS 8 on CD. No file extensions, as nothing did at the time. Just Type and Creator codes. They all open fine in PS CS5.5 in Snow Leopard, though the native Photoshop files do need to have a .psd extension added.

Unix Executable Files...why won't they open?

I now have a new iMac and using Mavericks 10.9.3. I used TimeMachine to transfer my files (that contained these strange "Exec" files after I had updated to Mavericks on my previous iMac) a number of these files turned into something called "Exec" files (Black rectangular icon with green "exec" in the upper left corner). and randomly appeariing in diff software. Have these files become corrupted? Should I trash them?
Thanks for any help
Julie

In the Finder, click on these Exec files and press command+I. If the file is an AppleWorks document (even with no extension) it will tell you that. If it is a UNIX shell script with owner+group+world execute permissions, or a compiled executable from source code, it will state that it is a UNIX Executable File.
In the Terminal application, you can use the file command to discern (usually) more accurately what these black Exec documents comprise. The filenames that I use below at random, were created on my machine.
file -b dictx2
Mach-O 64-bit executable x86_64
file -b mvim
POSIX shell script text executable
file -b fubar.cwk # Finder Get Info says it is an AppleWorks document, and opens nicely in LibreOffice
data
The decision to delete these depends on what they are, the purpose they may continue to serve, and in the case of word processing documents, content for retention consideration.

Unix Executable Files and VLC index.dat file -Samsung Digimax S800

Hi and thanks for any enlightenment in advance .
I got my new iMac in January and it's great . I'm using it mostly for games iWeb and pro apps like Logic . I continue to use my trusty old eMac for email and internet chores .
I was preparing to install Finale today and noticed the installation DVD had Adobe Reader 7.0.8 this led me to check "Adobe" with spotlight to make sure I already had it (I do) and I discovered a folder for Photoshop 7 settings so I looked to see if I had Photoshop (I don't:( ) , but I did find a folder titled Photoshop7 containing three files 2 Unix Executable Files titled AAAAAAAA2 and AAAAAAAA2M and a VLC index.dat file .
"Command I" tells me they are all 4KB and were created March 4 2007 and are located at Library/Application Support/Adobe/Filebrowser .
I think this was the time I was trying to get my new camera (Samsung Digimax S800) to download a movie . It didn't work and I have given up trying .
So my question is , " Can I delete these "
iMac 2.33 GHz- Powerbook - eMac Mac OS X (10.4.8)

Hi terence
Would I have any other adobe apps that came with my iMac besides Reader 7.0 ?
I appear to have opened a can off worms trying to open Adobe for the first time .
http://discussions.apple.com/thread.jspa?threadID=978019
iMac 2.33 GHz- Powerbook - eMac Mac OS X (10.4.8)

Fonts problems (unix executable file)

Hi,
I've a mac os x 10.4.11(tiger) G5 and a new mac os x 10.5.2(leopard)Imac both connected on a server.
I've many differents fonts on the server. On the G5, I can take all the fonts on the server, put them on my desktop and they will keep their extensions. On the Imac, when i do the same, only the *.ttf et *.otf are recognized, and all the others (font suitcase, postscript type 1 outline font, etc...) are known as unix executable file (0 ko). So, i've to go on my G5, create a zip file of the fonts, open my zip on my desktop's Imac (not on my server, because same problem) and then I've all my fonts with the right extension.
My font software is (on my both mac) is Linotype FontExplorer X Version 1.2.3.
What I've to do, to proceed in the same way on my Imac as on my G5, and not create a zip?
Thanks

I knew this sounded familiar. Mark Douma posted this on a very similar thread a while back.<hr>Notice the "__MACOSX" folder in the expanded archive? That's evidence that the original archive was created using the built-in "Create Archive" function of the Finder, but that the archive on your end was expanded using Stuffit Expander 8.0.1 or earlier.
ZIP files don't normally support resource forks, so when you create a zip file of fonts, the program needs to some method of preserving this information. In Stuffit Expander versions 8.0.1 and earlier, it used its own method to preserve this information (before creating the final zip file, it would first encode each included file as a MacBinary (.bin) file).
Unfortunately, the built-in "Create Archive" feature of the Finder (BomArchiveHelper.app, actually) uses a different method, one which you're seeing evidence in the "__MACOSX" folder in the images shown. Inside that folder are the "other halves" of the files you want to use.
There are two possible solutions:
1) Instead of using Stuffit Expander to expand the .zip files, use the built-in feature of OS X. To do this, select a .zip file in the Finder, and choose Command-i to open a Get Info window. In the Open With section, make sure that "BomArchiveHelper.app" (Tiger and earlier) or "Archive Utility.app" (Leopard) is set to open the archives. If it isn't, click the pop-up menu, choose Other, and navigate to the /System/Library/CoreServices/ folder and choose the appropriate application for your version of OS X. Then click the Change All button to apply this to all .zip files. Then locate the original .zip and expand it once again.
2) Update your version of Stuffit Expander to version 8.0.2 or later. Allume changed the method it used to preserve information in zip files to match that of the Finder's method in Expander 8.0.2 and later. After updating, locate the original .zip file and expand it once again.
There may also be an advanced way of salvaging these files shown toward the end of the following movie.
The following movie shows the predicament (I haven't had a chance to add sound or text, but it should hopefully be self-explanatory).
Notice the version of Stuffit Expander used to expand the archive is 8.0, which exhibits the same problematic behavior you're seeing:
http://homepage.mac.com/mdouma46/images/zipFilesAndFonts.mov (~8.0 MB).
Hope this helps.... <hr>
Essentially, it's all in how the fonts were compressed or sent. Trying to send Mac fonts as direct attachments in an email will almost certainly ruin them. As Mark stated above, how they were zipped and then unzipped can also create empty fonts.

Unix executable File _VUC69~7 in OSX10.4.11

A unix executable file named "_VUC69~7" has appeared in the finder on the top level of my main hard drive.
Curious - any ideas what it is, why it's appeared & whether I can or should make it disappear?
Many thanks in advance, P.

Many thanks, I had found these links but not sure they are relevant to my situation -- just a powermac & a wireless internet connection.
I wasn't aware that I was using Samba, would it run without my knowledge?
Also have never knowingly set up a Linux file server -- are these all things that happen "under the hood" that an average user doesn't realise are going on?
The file was created last March but I can't think what I did around this time that would have created it.

How to import unix executable files into Final Cut Pro

A friend wanted me to create a Halo 3 Montage Video for him. He loaded the saved clips onto a flash drive for me but when I put it into my computer the information comes up as Unix Executable Files and I don't know how to import them into Final Cut Pro 7.0.2 or if it's even possible. Any help would be much appreciated. Thanks.

Ok. Well, I plug in the flash drive. When it opens there's a folder that says XBox360. When I click on the folder there are 9 files listed that say Data0000, Data0001 etc. The preview option shows a gray folder that says Exec on it and the only information I can find is that it's a Unix Executable File. When I click on more info option everything that pops up is what I've already told you. I tried opening it in the VLC Player but nothing played which makes me think there aren't video files on the flash drive. When I click on the file to open it the Terminal Program appears and lists basic information about the file.
Is there a program that can take these files and covert them into something that can run in Final Cut Pro? Or is that what VLC is supposed to do?

What is an unix executable file that appeared in my folder?

HI,
In my folders structure I have a folder named "jobs: where I put my working files etc.
Yesterday inside the "jobs" folder I found a file with the same name "jobs" , its icon is dark gray and it is a "unix executable file" with zero bytes...
How was it created there?
I think I did a permission repair this week, but this is the first time I see a Unix exec file ...

** folder named "jobs:" **
When I tried to create a folder with that name, the Finder told me that the name was not valid. A colon in a Mac file or folder name used to be a bad idea. I guess it still is. I'd rename that folder to exclude the colon.

Need help opening Unix Executable Files

I've recently been given the task of updating various files containing instruction manuals. However, the person who created these files is long gone and no one seems to know what program they were created in. All I know is that they are listed as "Unix Executable File" when I click on the document. I've tried opening them in TextEdit and this does me no good. Does anyone know how I can determine what program these files were originally created in so that I can open them?

Files that have no filename extensions (used by Windows and OS X, but not by OS 9) and have lost their Type and Creator codes (used by OS 9, but not by Windows or OS X), and are then written to a DOS-formatted disc by OS 9 and copied back to a Mac disc, are usually if not always misidentified by the OS X Finder as Unix executables.
Your company's old files, created in applications that ran in OS 9, probably have never had any filename extensions. Their Type and Creator codes have evidently been lost; those are what OS 9 uses to link the files to the applications that created them. If the files have also been written by OS 9 to any disk or flash drive formatted for Windows, i.e. FAT16 or FAT32, they have also lost their resource forks. The resource fork is a portion of a Mac file that has no analogous structure in a PC file. When a Mac file that contains data in its resource fork is written by OS 9 to a PC-formatted storage device, there's no place in the Windows file structure for that data — so it is simply discarded. When the Mac file is later copied back onto a Mac-formatted storage device, its resource fork is gone along with whatever data it contained, and the file may for all practical purposes be destroyed. OS X handles writing Mac files to Windows-formatted drives more gracefully, but passing files back and forth between OS 9 and OS X via a Windows-formatted storage device is asking for trouble.
I don't know just what practices have been used in moving these files from the Macs they were created on to the one you're trying to open them on now, but I suspect there has been some unwitting demolition in the process.
If copies of these files are still stored on the old Mac on which they were created, and that Mac still works, get on it and double-click the saved copies of the files to open them in the program(s) that created them, and make notes of which application opens each of the files. Be aware that the folder structure containing the files may have to be preserved exactly as it is for the files to open properly — do not reorganize anything. It may be essential, for example, for a PageMaker file to be kept in the same folder as all the individual files that have been "placed" in it using the Place command in PageMaker. If any of those files are moved elsewhere, they may be missing from the PageMaker document when it opens. I've never used Quark or Freehand, so I don't know whether they have the same requirement, or other requirements that are less than obvious.
Any of the old manuals that you're able to open in their original applications can be saved as PDF files using an invaluable OS 9-based "printer driver" called PrintToPDF. They can then be opened in Adobe Reader or Preview on your G5 running OS X, though you won't be able to edit them easily. If you require the ability to edit these files on the G5, rather than on the old computer using the apps that originally created them, you will need first to discover which OS 9-based application created each one, and then ascertain what if any current OS X-based application is able to open the file format used by that old application. In the case of PageMaker files, that will probably be Adobe InDesign or nothing. InDesign may also open old Quark files; I don't know. Aldus or Adobe Freehand files may be openable using Adobe Illustrator. These are just guesses.
Dragging and dropping the files onto MS Word or TextWrangler may reveal, buried somewhere in them, the name of the application(s) that created them. I know a PageMaker file, opened as plain text, will always contain the word "PageMaker". As for other file formats, I'm not sure.
Message was edited by: eww
Message was edited by: eww

Autosaved as Unix Executable Files after editing font size?

When I open a .txt file in TextEdit, and change the font, in the Finder I see a new Unix Executable File appear, with (Autosaved) after the file name. This is in addition to the original .txt file - so there are now 2 files of the same name showing.
However, when I manually save the file, the Unix exe file disappears from the Finder, leaving the newly saved .txt file.
Is this normal? If not, please let me know what else I can try to fix it. I've already tried both suggestions in this thread & neither of them worked.
Thanks!

Ok I noticed that TextEdit preferences shows an option to "delete the automatic backup file" so that's why it's disappearing...
...but what happens if TextEdit quits on me unexpectedly (which it has before)? Will I be able to open the autosaved Unix executable file with TextEdit or will it be "unrecognized?"
If anyone can give me confirmation that their autosaved files are Unix exe files and/or if they've been able to open the Unix exe backup files in the program they were created from, that would help.

Converting Unix Executable Files for use in DVD Studio Pro

I have several projects that were created in iDVD 2 back in 2002. In Finder, the file kind is listed as Unix Executable Files. If I add the extension .dvdproj using Get Info and try to open them in DVD Studio Pro, I get the error Wrong File Format and it will not open the project.
The machine I am currently using does not have iDVD on it.
Does anyone have a recommendation on a way to make these files usable for DVD Studio Pro? I understand if it is not possible.

You can import iDVD project into DVD Studio Pro, however I think it won't work with projects from iDVD 5. I'm not sure about iDVD 2. Also these files have no extension and are listed as Unix Executable Files.

HT1349 how do you import video to Aperture from a dvd with a unix executable file

how do you import video to Aperture or imovie from a dvd with a unix executable file?

Allan's suggestion of using the iDisk will work but will fill up the iDisk unless you do housecleaning occasionally. Another, non Apple way would be to upload them to an account on Twango.com. It sort of like MyTube but for photos and videos and is more personal in nature. It's free (monthly uploads are limited to 250MB/mo) and others can easily pop into your public channel (individual sections of a person's account are called channels) and download whatever size you want. You can select the size of your uploads from full sized to 1600, 1024 or 640 pixels max. What I like about the site is that you can email photos to your account. Makes it rather easy. You can also add slideshows and a ticker tape type of display from Twango to web pages (they create the code to use for the channel you select) like this. It's not an Apple thing but I've found it's quick. May or may not be what you're looking for.
Do you Twango?
G5 Dual Core 2GHz, 2G RAM, 250G HD; G4 Dual 1Ghz, 1.5G RAM, 80G HD, Mac OS X (10.4.7) 22 LCD Display, 200G & 160G FW HDs, Canon S400, i850 & LIDE 50, Epson R200

Word documents appear as "unix executable files" and cannot be opened

Hi: I am running 10.5.5 on my Intel Imac. The problem is that many old MS Word documents have suddenly flipped into documents with no file extension, but which are identified in the Preview window as "unix executable files."
I've had this happen before, and all I had to do was add the .doc extension for them to become Word documents again. This time there is nothing I can do to change them over. I have tried opening them from Word, from Pages, from Text Edit, with no results. (I have also used all the possibilities available from Word as well).
There doesn't seem to be any pattern -- random documents in the same folder, created at the same time and modified at the same time, appear as unix files, while the others seem fine. Any ideas?
<Post Relocated by Moderator>

This is the iWeb forum. You should post your question in the Leopard forum. But I'll give a try at a possible solution:
1 - check the Finder preferences and make sure you have the option to show file extensions checked.
2 - select one of the Work files, type Command+i and in the Info window go to the Open With menu and select Word as the default application. Then click on the Apply to All... button.
OT

Thumbs.db, Unix Executable Files, and RTF

Please can anyone help with the following?
1. Thumbs.db - What are these files that seem to create themselves?
2. Unix Executable Files – some old Word files (from PC days) have converted themselves somehow to this format.
3. Some Word files (from PC days) are now RTF files.
Any clarification would be appreciated. thanks.

1. Those are associated, on my machine, with Turbo Tax.
2. Add .doc to those and they should revert to Word files.
3. Change .rtf to .doc.

Create Unix Executable file

Similar Messages

Maybe you are looking for