OK, close.
** Changed in: lsb (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/532341
Title:
Suddenly start_daemon does not fork the new pid, hangs the script
The ooRexx developers figured out that this problem was due to a bug in
how the C/C++ code was compiling. Some code specifically for AIX was
ending up in the Linux builds. They are releasing an updated version,
4.0.1 soon that has this corrected. I have verified the fix on a 9.10
and 10.04 box.
Tested with a clean VM load of the Lucid alpha today - 20100312. Still
the same problem.
At boot up, the start_daemon does not fork the new pid, hangs the
script, prevents the machine from getting to the tty1 login prompt.
Kill the rxapi process, start script exits normally.
Manually start /
This problem also affects the fully updated version of the Lucid Alpha.
For some reason when the operation system boots, it is unable to fork
the daemon.
If I kill the daemon, then the start script does finish / exit, which
cleans up the environment.
However manually starting stopping the
I was able to recreate this problem in a VirtualBox test environment.
Steps to recreate this situation:
1) Install Ubuntu Server 9.10
2) Apply all available updates
3) Reboot
4) Add openssh-server
5) ssh to the VM test server
6) use wget to DL the latest ooRexx for Ubuntu:
wget
I guess I never rebooted this server since I had installed ooRexx.
Now I was able to recreate this problem on Ubuntu Server 9.10 without
any updates applied.
Updating both tickets with this information.
--
Suddenly start_daemon does not fork the new pid, hangs the script
