03-30-2010
You ever think about just loading the launchd item and using the ondemand or watch path option?
How are you checking if applications crash?
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I am a newbie here. Trying to find a way of writing a script to launch multiple terminal or console windows on solaris 9. I used to be able to do this using cmdtool on older versions of solaris and it was even possible to configure the size and screen position of the window and the title. ... (5 Replies)
Discussion started by: omerta
5 Replies
2. Shell Programming and Scripting
I am running Mac OS X (10.5). I run the following script successfully in terminal in order to split an mp3 file into 3 smaller mp3 files...
split -b 8667k -a1 Monday.mp3 Levin-Hour_; ls Lev* | sed "s/.*/mv '&' '&.mp3'/g" | zsh
However, when I run a similar script within the Applescript editor... (2 Replies)
Discussion started by: tgaleza
2 Replies
3. Shell Programming and Scripting
I developed a script in Lingon (which is an automated script editor developed for OS X) that is used to automatically restart programs only if they crash. The script itself does just that, but I only want it to load if I'm going to use the specific application that it's designed to protect. In... (3 Replies)
Discussion started by: JFraser1
3 Replies
4. Shell Programming and Scripting
Hello,
I have a PERL-TK based GUI from which I want to launch a command on an existing UNIX terminal (this is also the parent terminal for this perl based gui window). The command I want to launch is interactive (there is no intention to interact with that command from the same PERL gui i.e. no... (2 Replies)
Discussion started by: AnuragJindal
2 Replies
5. OS X (Apple)
What I want my script to do is to run a command in Terminal and close that same Terminal window when the process is complete.
Of course I could ad a delay of 6 seconds to complete the process, but it may not be enough every time.
To simplify my question, this is what I want to achieve.... (9 Replies)
Discussion started by: ShadowofLight
9 Replies
6. OS X (Apple)
After I installed OS X Lion I haven't been able to launch x11 remotely (using ssh) from Terminal.
It works fine locally, and also remotely directly from the Xterm.
I log in to the unix server at my university from the terminal like this:
ssh -l -X login@host.com
This used to launch... (1 Reply)
Discussion started by: gnyrf
1 Replies
7. Shell Programming and Scripting
I'm new using Unix commands in applescript. The following script you choose different folders with PDfs, get file count of PDfs on chosen folders, & write the results in text file.
set target_folder to choose folder with prompt "Choose target folders containing only PDFs to count files" with... (0 Replies)
Discussion started by: nellbern
0 Replies
8. Red Hat
After installing centos iam not able to see the terminal icon in the applications menu to launch the command prompt in Centos.
However iam able to see the Open Terminal menu, when i right click and it is not working.
let me know what are the things i need to check.:b: (1 Reply)
Discussion started by: Kesavan
1 Replies
9. Shell Programming and Scripting
The following command works perfectly in Terminal, but not in Applescript. (Returns "unknown token" error for square brackets.)
(new to site. sorry.)
I have an Applescript that is designed to find and remove any square-bracketed text, including the square brackets.
I ran the following code from... (1 Reply)
Discussion started by: Phillip Acosta
1 Replies
10. Shell Programming and Scripting
I have been having an extremely annoying problem. For the record, I am relatively new at this. I've only been working with unix-based OS's for roughly two years, mostly Xubuntu and some Kali. I am pretty familiar with the BASH language, as that's the default shell for debian. Now, I've made this... (16 Replies)
Discussion started by: Huitzilopochtli
16 Replies
LEARN ABOUT MOJAVE
launch
launch(3) BSD Library Functions Manual launch(3)
NAME
launchd APIs -- interfaces for interacting with a launchd job.
SYNOPSIS
#include <launch.h>
#include <servers/bootstrap.h>
kern_return_t
bootstrap_check_in(mach_port_t bp, const name_t service_name, mach_port_t *sp);
int
launch_activate_socket(const char *name, int **fds, size_t *cnt);
DESCRIPTION
A launchd(8) job may have resources that are held on behalf of it while it is not running to facilitate launch-on-demand. These interfaces
allow for the job to retrieve these resources as part of its initialization.
Currently supported resource types are XPC listener connections, Mach ports, and sockets. Use of XPC with launchd(8) is documented in the
xpc(3) family of manual pages.
MACH PORTS
The bootstrap_check_in() routine allows for a launchd(8) job to retrieve the receive right to a Mach port that launchd(8) has created on
behalf of the job. launchd(8) creates this port and advertises it in the appropriate Mach bootstrap namespace by parsing the MachServices
entry of the job's launchd.plist(5). The first argument to bootstrap_check_in() should always be the bootstrap_port() global. The second
argument should be the name of the service whose port you wish to retrieve, as specified as an entry in the job's MachServices dictionary.
The final argument, upon successful return, will be the name of the receive right corresponding to the port that launchd(8) had advertised in
the bootstrap namespace.
If the job closes the receive right to the port with mach_port_mod_refs() or exits, the receive right obtained by this routine will be send
back to launchd(8) rather than being closed. This allows launchd to resume advertising the same port in the Mach bootstrap namespace and
frees clients from the need to re-query for the send right to that port when the job dies.
SOCKETS
The launch_activate_socket() routine allows a launchd(8) job to retrieve a set of file descriptors corresponding to a socket service that
launchd(8) has created and advertised on behalf of the job by parsing the Sockets entry in the job's launchd.plist(5). The first argument
should be the name of the socket entry as specified in the launchd.plist(5). The second argument, upon output, will point to an array of
integers whose count is filled into the third argument upon success. This array represents all the sockets that launchd(8) created corre-
sponding to the entry in the job's Sockets dictionary. Depending on the properties specified, a single Sockets entry may have multiple
descriptors created for it (one for IPv4 and one for IPv6, for example). This array is allocated on the heap, and it is the caller's respon-
sibility to call free(3) to dispose of the memory when it is no longer needed.
RETURN VALUES
If launch_activate_socket() succeeds, zero is returned. In the event of failure, a non-zero POSIX-compatible error code indicating the nature
of the error is returned. This error may be decoded with strerror(3).
If bootstrap_check_in() succeeds, KERN_SUCCESS is returned. In the event of failure, a non-zero error code that may be decoded with
bootstrap_strerror().
ERRORS
bootstrap_check_in() will fail if:
[BOOTSTRAP_UNKNOWN_SERVICE]
The Mach service name specified does not exist in the caller's launchd.plist(5).
[BOOTSTRAP_SERVICE_ACTIVE]
The specified Mach service has already been checked in by the job.
launch_activate_socket() will fail if:
[ENOENT] The socket name specified does not exist in the caller's launchd.plist(5).
[ESRCH] The calling process is not managed by launchd(8).
[EALREADY] The specified socket has already been activated.
SEE ALSO
xpc(3), xpc_connection_create(3), socket(2), launchd(8), launchd.plist(5).
Darwin 31 March, 2014 Darwin