[Bug 152875] Re: ddclient spawns several competing daemons
Yup, exactly, that's what I found out the hard way too ;) My suggestion would be either effectively keeping these two options from running together (for example by checking for a running instance before spawning another one?) or at least adding a sentence to the config file so people are aware that these two options exclude each other. Thanks! -- ddclient spawns several competing daemons https://bugs.launchpad.net/bugs/152875 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152875] ddclient spawns several competing daemons
Public bug reported: Binary package hint: ddclient I am running Ubuntu Feisty. I have a DSL line that gets disconnected every 24 hours, then upon a reconnect gets a new IP address. When I set both of the following settings in /etc/default/ddclient to true... # Set to "true" if ddclient should be run every time a new ppp connection is # established. This might be useful, if you are using dial-on-demand run_ipup="true" # Set to "true" if ddclient should run in daemon mode run_daemon="true" ...then ddclient will over time spawn several, competing ddclient daemon processes (when I noticed the issue I had 3 of them) that will almost constantly execute update requests on the dyndns server. This got me temporarily banned from dyndns.org, until I set run_ipup to false and kept the run_daemon option as true, which will work fine. My ddclient is configured to get its IP address from the interface ppp0. ** Affects: ddclient (Ubuntu) Importance: Undecided Status: New -- ddclient spawns several competing daemons https://bugs.launchpad.net/bugs/152875 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95210] Re: Can't access to TTY- init /etc/event.id/tty1:16: Unknown stanza
*** This bug is a duplicate of bug 89314 *** https://bugs.launchpad.net/bugs/89314 Yeah. Glad I have SSH access to the box, too. Fixing the last line made the issue go away for me too. -- Can't access to TTY- init /etc/event.id/tty1:16: Unknown stanza https://bugs.launchpad.net/bugs/95210 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87745] Re: Root fs on LVM on mdadm fails to boot
So, is there a way for us to backport the fixed package into Feisty (or at least apply a workaround)? Upgrading the entire system to a development version doesn't seem useful to solve this problem alone, as we likely buy into other, development-typical issues then. Thanks! -- Root fs on LVM on mdadm fails to boot https://bugs.launchpad.net/bugs/87745 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95210] Re: Can't access to TTY- init /etc/event.id/tty1:16: Unknown stanza
*** This bug is a duplicate of bug 89314 *** https://bugs.launchpad.net/bugs/89314 @Flapane: This is how a corrupt file looks like: # tty1 - getty # # This service maintains a getty on tty1 from the point the system is # started until it is shut down again. start on runlevel 2 start on runlevel 3 start on runlevel 4 start on runlevel 5 stop on runlevel 0 stop on runlevel 1 stop on runlevel 6 respawn /sbin/getty 38400 tty1exec /sbin/getty 38400 tty1 -- Can't access to TTY- init /etc/event.id/tty1:16: Unknown stanza https://bugs.launchpad.net/bugs/95210 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
