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 tha
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 sho
*** 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
Y
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 m
*** 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 runle
