Creating a guessable tmp file in a public area like /tmp is a security risk.
It is safer to leave such a file, so the next time it is overwritten not created.
There a methods for a safer tmp file, see
Most safe is to avoid a tmp file. E.g. by using | and (sub shell).
Hi
im using the following to copy a file to a directory, the user being prompted to overwrite if the file already exists in that directory,
cp -i myfile /home/brief/bin2
but this reveals the path of the directory when being prompted to overwrite (below)
cp: overwrite... (2 Replies)
Dear All,
I have text file like this:
Header
Record 1
Record 2
.......
Record n
Tail
This line of code :
awk '{ if ( NR == 1 ) { head=substr($0,1,300);} else { last = substr($0,1,300);}END{printf "Header is : %-300s Trailer is : %-300s\n", head, last}' filename
converted Header... (11 Replies)
Hi guys,
I checked the knowledge base before posting this question.
is there any way by which you can ALWAYS ALLOW file overwrite in AWK?. i.e. an option similar to noclobber in Korn shell.
I don't to check for files existence and remove them. (1 Reply)
I'm debugging a ksh script written by someone else that does the following:
It runs a command and redirects stdout to a file called dberror that already exists using ">". This command fails with the following error:
The file access permissions do not allow the specified action. dberror:... (1 Reply)
my script is:
awk '...mycode...' file1.txt > file2.txt
and i want to overwrite file2.txt eachtime I run this script. but it says:File exists! :( I have tried
awk '...mycode...' file1.txt >| file2.txt but it again says:Missing name for redirect! :confused::confused:
what is this? (2 Replies)
How do you overwrite a directory with another directory? I know you can delete your directory then copy your directory over, but I would think there would be a way to do this in one step. (5 Replies)
Dear users,
I've been looking for a way to overwrite files only if both have the same size, how could I do this? any help is very appreciated.
Best regards,
Gery (5 Replies)
Hi Friends,
I have written a script to capture system performance every hour and redirected to output file. How to overwrite the file every next day?
Thanks
Suresh (4 Replies)
Discussion started by: suresh3566
4 Replies
LEARN ABOUT MOJAVE
osacompile
OSACOMPILE(1) BSD General Commands Manual OSACOMPILE(1)NAME
osacompile -- compile AppleScripts and other OSA language scripts
SYNOPSIS
osacompile [-l language] [-e command] [-o name] [-d] [-r type:id] [-t type] [-c creator] [-x] [-s] [-u] [-a arch] [file ...]
DESCRIPTION
osacompile compiles the given files, or standard input if none are listed, into a single output script. Files may be plain text or other
compiled scripts. The options are as follows:
-l language
Override the language for any plain text files. Normally, plain text files are compiled as AppleScript.
-e command
Enter one line of a script. Script commands given via -e are prepended to the normal source, if any. Multiple -e options may be given
to build up a multi-line script. Because most scripts use characters that are special to many shell programs (e.g., AppleScript uses
single and double quote marks, ``('', ``)'', and ``*''), the command will have to be correctly quoted and escaped to get it past the
shell intact.
-o name
Place the output in the file name. If -o is not specified, the resulting script is placed in the file ``a.scpt''. The value of -o
partly determines the output file format; see below.
-x Save the resulting script as execute-only.
The following options are only relevant when creating a new bundled applet or droplet:
-s Stay-open applet.
-u Use startup screen.
-a arch
Create the applet or droplet for the specified target architecture arch. The allowable values are ``ppc'', ``i386'', and ``x86_64''.
The default is to create a universal binary.
The following options control the packaging of the output file. You should only need them for compatibility with classic Mac OS or for cus-
tom file formats.
-d Place the resulting script in the data fork of the output file. This is the default.
-r type:id
Place the resulting script in the resource fork of the output file, in the specified resource.
-t type
Set the output file type to type, where type is a four-character code. If this option is not specified, the creator code will not be
set.
-c creator
Set the output file creator to creator, where creator is a four-character code. If this option is not specified, the creator code will
not be set.
If no options are specified, osacompile produces a Mac OS X format script file: data fork only, with no type or creator code.
If the -o option is specified and the file does not already exist, osacompile uses the filename extension to determine what type of file to
create. If the filename ends with ``.app'', it creates a bundled applet or droplet. If the filename ends with ``.scptd'', it creates a bun-
dled compiled script. Otherwise, it creates a flat file with the script data placed according to the values of the -d and -r options.
EXAMPLES
To produce a script compatible with classic Mac OS:
osacompile -r scpt:128 -t osas -c ToyS example.applescript
SEE ALSO osascript(1), osalang(1)Mac OS X November 12, 2008 Mac OS X