imported>Supportadmin: /* child_process.spawn(command, [args], [options]) */

2013-08-24T11:13:28Z

child_process.spawn(command, [args], [options])

imported>Supportadmin: /* child.pid */

2013-08-24T10:36:08Z

child.pid

← Предыдущая версия		Версия от 13:36, 24 августа 2013
Строка 64:		Строка 64:

	====child.pid====		====child.pid====
	Integer		'''Integer'''

	The PID of the child process.		The PID of the child process.

	Example:		Example:

	var spawn = require('child_process').spawn,		<nowiki>var spawn = require('child_process').spawn,
	grep = spawn('grep', ['ssh']);		grep = spawn('grep', ['ssh']);

	console.log('Spawned child pid: ' + grep.pid);		console.log('Spawned child pid: ' + grep.pid);
	grep.stdin.end();		grep.stdin.end();</nowiki>
	child.kill([signal])#		====child.kill([signal])====
	signal String		'''signal String'''

	Send a signal to the child process. If no argument is given, the process will be sent 'SIGTERM'. See signal(7) for a list of available signals.		Send a signal to the child process. If no argument is given, the process will be sent 'SIGTERM'. See signal(7) for a list of available signals.

	var spawn = require('child_process').spawn,		<nowiki>var spawn = require('child_process').spawn,
	grep = spawn('grep', ['ssh']);		grep = spawn('grep', ['ssh']);

Строка 86:		Строка 88:

	// send SIGHUP to process		// send SIGHUP to process
	grep.kill('SIGHUP');		grep.kill('SIGHUP');</nowiki>

	May emit an 'error' event when the signal cannot be delivered. Sending a signal to a child process that has already exited is not an error but may have unforeseen consequences: if the PID (the process ID) has been reassigned to another process, the signal will be delivered to that process instead. What happens next is anyone's guess.		May emit an 'error' event when the signal cannot be delivered. Sending a signal to a child process that has already exited is not an error but may have unforeseen consequences: if the PID (the process ID) has been reassigned to another process, the signal will be delivered to that process instead. What happens next is anyone's guess.

Строка 93:		Строка 96:
	See kill(2)		See kill(2)

	child.send(message, [sendHandle])#		====child.send(message, [sendHandle])====
	message Object		'''message Object'''
	sendHandle Handle object
			'''sendHandle Handle object'''

	When using child_process.fork() you can write to the child using child.send(message, [sendHandle]) and messages are received by a 'message' event on the child.		When using child_process.fork() you can write to the child using child.send(message, [sendHandle]) and messages are received by a 'message' event on the child.

	For example:		For example:

	var cp = require('child_process');		<nowiki>var cp = require('child_process');

	var n = cp.fork(__dirname + '/sub.js');		var n = cp.fork(__dirname + '/sub.js');
Строка 108:		Строка 113:
	});		});

	n.send({ hello: 'world' });		n.send({ hello: 'world' });</nowiki>
	And then the child script, 'sub.js' might look like this:		And then the child script, 'sub.js' might look like this:

	process.on('message', function(m) {		<nowiki>process.on('message', function(m) {
	console.log('CHILD got message:', m);		console.log('CHILD got message:', m);
	});		});

	process.send({ foo: 'bar' });		process.send({ foo: 'bar' });</nowiki>
	In the child the process object will have a send() method, and process will emit objects each time it receives a message on its channel.		In the child the process object will have a send() method, and process will emit objects each time it receives a message on its channel.

Строка 124:		Строка 129:
	Emits an 'error' event if the message cannot be sent, for example because the child process has already exited.		Emits an 'error' event if the message cannot be sent, for example because the child process has already exited.

	Example: sending server object#		====Example: sending server object====

	Here is an example of sending a server:		Here is an example of sending a server:

	var child = require('child_process').fork('child.js');		<nowiki>var child = require('child_process').fork('child.js');

	// Open up the server object and send the handle.		// Open up the server object and send the handle.
Строка 137:		Строка 142:
	server.listen(1337, function() {		server.listen(1337, function() {
	child.send('server', server);		child.send('server', server);
	});		});</nowiki>
	And the child would the receive the server object as:		And the child would the receive the server object as:

	process.on('message', function(m, server) {		<nowiki>process.on('message', function(m, server) {
	if (m === 'server') {		if (m === 'server') {
	server.on('connection', function (socket) {		server.on('connection', function (socket) {
Строка 146:		Строка 151:
	});		});
	}		}
	});		});</nowiki>

	Note that the server is now shared between the parent and child, this means that some connections will be handled by the parent and some by the child.		Note that the server is now shared between the parent and child, this means that some connections will be handled by the parent and some by the child.

	For dgram servers the workflow is exactly the same. Here you listen on a message event instead of connection and use server.bind instead of server.listen. (Currently only supported on UNIX platforms.)		For dgram servers the workflow is exactly the same. Here you listen on a message event instead of connection and use server.bind instead of server.listen. (Currently only supported on UNIX platforms.)

	Example: sending socket object#		====Example: sending socket object====

	Here is an example of sending a socket. It will spawn two children and handle connections with the remote address 74.125.127.100 as VIP by sending the socket to a "special" child process. Other sockets will go to a "normal" process.		Here is an example of sending a socket. It will spawn two children and handle connections with the remote address 74.125.127.100 as VIP by sending the socket to a "special" child process. Other sockets will go to a "normal" process.

	var normal = require('child_process').fork('child.js', ['normal']);		<nowiki>var normal = require('child_process').fork('child.js', ['normal']);
	var special = require('child_process').fork('child.js', ['special']);		var special = require('child_process').fork('child.js', ['special']);

Строка 170:		Строка 176:
	normal.send('socket', socket);		normal.send('socket', socket);
	});		});
	server.listen(1337);		server.listen(1337);</nowiki>
	The child.js could look like this:		The child.js could look like this:

	process.on('message', function(m, socket) {		<nowiki>process.on('message', function(m, socket) {
	if (m === 'socket') {		if (m === 'socket') {
	socket.end('You were handled as a ' + process.argv[2] + ' person');		socket.end('You were handled as a ' + process.argv[2] + ' person');
	}		}
	});		});</nowiki>
	Note that once a single socket has been sent to a child the parent can no longer keep track of when the socket is destroyed. To indicate this condition the .connections property becomes null. It is also recommended not to use .maxConnections in this condition.		Note that once a single socket has been sent to a child the parent can no longer keep track of when the socket is destroyed. To indicate this condition the .connections property becomes null. It is also recommended not to use .maxConnections in this condition.

	child.disconnect()#		===child.disconnect()===
	To close the IPC connection between parent and child use the child.disconnect() method. This allows the child to exit gracefully since there is no IPC channel keeping it alive. When calling this method the disconnect event will be emitted in both parent and child, and the connected flag will be set to false. Please note that you can also call process.disconnect() in the child process.		To close the IPC connection between parent and child use the child.disconnect() method. This allows the child to exit gracefully since there is no IPC channel keeping it alive. When calling this method the disconnect event will be emitted in both parent and child, and the connected flag will be set to false. Please note that you can also call process.disconnect() in the child process.

	child_process.spawn(command, [args], [options])#		===child_process.spawn(command, [args], [options])===
	command String The command to run		command String The command to run

	args Array List of string arguments		args Array List of string arguments

	options Object		options Object

	cwd String Current working directory of the child process		cwd String Current working directory of the child process
	stdio Array\|String Child's stdio configuration. (See below)		stdio Array\|String Child's stdio configuration. (See below)

imported>Supportadmin в 10:29, 24 августа 2013

2013-08-24T10:29:24Z

Внесённые изменения

imported>Supportadmin: Новая страница: «Node обеспечивает трёх-направленный POPEN (3) для модуля child_process. Поток данных можно направля…»

2013-08-24T10:27:37Z

Новая страница: «Node обеспечивает трёх-направленный POPEN (3) для модуля child_process. Поток данных можно направля…»

Новая страница

Node обеспечивает трёх-направленный POPEN (3) для модуля child_process.

Поток данных можно направлять через стандартные stdin, stdout и stderr дочернего процесса в полностью неблокирующем стиле. (Заметим, что некоторые программы используют внутреннюю линейную буферизации строк ввода/вывода. Это не влияет node.js, но это означает что информация, передаваемая дочернему процессу "потребляется" им не сразу.)

Для создания дочернего процесса используйте require('child_process').spawn() или require('child_process').fork(). Семантика каждого немного отличается, и описана ниже.

Child Process - История изменений

imported>Supportadmin: /* child_process.spawn(command, [args], [options]) */

imported>Supportadmin: /* child.pid */

imported>Supportadmin в 10:29, 24 августа 2013

imported>Supportadmin: Новая страница: «Node обеспечивает трёх-направленный POPEN (3) для модуля child_process. Поток данных можно направля…»