Davide Ancri
|
Script spawned on qnx 6.5.0 remote node (on -f) fails with "cannot fork"
|
Davide Ancri
01/09/2015 5:53 AM
post112890
|
Script spawned on qnx 6.5.0 remote node (on -f) fails with "cannot fork"
hello there
QNX 6.5.0 over x86 arch boxes, connected with qnet: it seems that a very simple script spawned on a remote node (from a
non-root shell) is unable to start any process, failing with the message:
cannot fork - try again
The same script, launched with the same "on -f" command, can be run without problems in the following cases:
- from a root shell, if system is based on qnx 6.5.0
- from a non-root shell, if system is based on qnx 6.4.1
Is there some new restriction about scripts privileges under qnx 6.5.0 ? Or how can I get back to the good old behaviour
?
Here are some commands showing infos about my system and what I get from the script execution in different cases:
user@bart /home/user$ pidin net
ND Node CPU Release FreeMem BootTime
0 bart 1 X86 6.5.0 2386Mb/2573Mb Jan 08 16:37:58 CET 2015
Processes: 48, Threads: 121
CPU 1: 131758 Intel 686 F6M12S2 2401MHz FPU
1 ppu10 1 X86 6.5.0 2739Mb/2929Mb Jan 08 16:38:13 CET 2015
Processes: 21, Threads: 50
CPU 1: 131758 Intel 686 F6M12S2 2400MHz FPU
user@bart /home/user$ cat ./dap
sleep 1
echo done!
user@bart /home/user$ ls -la ./dap
-rwxrwxr-x 1 user users 20 Jan 09 11:00 ./dap
user@bart /home/user$ ./dap
done!
user@bart /home/user$ on -f ppu10 ./dap
./dap[1]: cannot fork - try again
user@bart /home/user$ su
password:
#
# on -f ppu10 ./dap
done!
thanks in advance!
Davide
|
|
|