It's still the same here. I will move to another syslog package today,
likely rsyslog or sysklogd.
# /etc/init.d/syslog-ng restart
* Stopping system logging syslog-ng
[fail]
* Starting system logging syslog-ng
JFI: I'm using syslog-ng successfully with OpenVZ (I suppose you are
using Linux VServer?).
--
[hardy] restart of syslog-ng fails in vserver
https://bugs.launchpad.net/bugs/220274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Nominating for hardy in case it shall turn out that this is indeed fixed
in a later release.
--
[hardy] restart of syslog-ng fails in vserver
https://bugs.launchpad.net/bugs/220274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
I'm sorry. I won't update my vserver to intrepid or jaunty anytime
soon. I request that somebody else please verify.
** Changed in: syslog-ng (Ubuntu)
Status: Incomplete => New
--
[hardy] restart of syslog-ng fails in vserver
https://bugs.launchpad.net/bugs/220274
You received this bug
Is this symptom still reproducible in 8.10 or 9.04?
** Changed in: syslog-ng (Ubuntu)
Status: New => Incomplete
--
[hardy] restart of syslog-ng fails in vserver
https://bugs.launchpad.net/bugs/220274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
still fails in hardy, ver 2.0.9-1ubuntu1
# /etc/init.d/syslog-ng restart
* Stopping system logging syslog-ng
[fail]
* Starting system logging syslog-ng
