Your message dated Sat, 20 Jul 2019 21:49:10 +0000
with message-id <[email protected]>
and subject line Re: Bug#622970: Reassigned to insserv #622970
has caused the Debian Bug report #622970,
regarding insserv: Converted to dependency-based boot sequence but did not 
delete flag file /etc/init.d/.legacy-bootordering
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
622970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622970
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: resolvconf
Severity: normal

Hi.  I am opening a new report for this since it's not necessarily the case
that this is the same problem as in #580288.  I will reply to the new report
once it's open.

-- 
Thomas Hood


On 16/04/11 07:35, Gregor Horvath wrote to #580288:
> Hi,
> 
> I am experiencing the same bug, but not with dhcp but with a static IP
> configuration. Please see attached the required information.
> I also noticed the following errors in /var/log/boot:
>                                      
> Sat Apr 16 07:25:02 2011: Configuring network interfaces...resolvconf:
> Error: /etc/resolvconf/run/interface is not a directory 
> Sat Apr 16 07:25:02 2011: run-parts: /etc/network/if-up.d/000resolvconf
> exited with return code 1 
> Sat Apr 16 07:25:03 2011: resolvconf:
> Error: /etc/resolvconf/run/interface is not a directory 
> Sat Apr 16 07:25:03 2011: run-parts: /etc/network/if-up.d/000resolvconf
> exited with return code 1 Sat Apr 16 07:25:03 2011:
> grep: /etc/resolv.conf: No such file or directory
> 
> --
> Greg
Sat Apr 16 07:25:02 2011: Setting preliminary keymap...done.
Sat Apr 16 07:25:02 2011: Setting parameters of disc: (none).
Sat Apr 16 07:25:02 2011: Activating swap...done.
Sat Apr 16 07:25:02 2011: Checking root file system...fsck from util-linux-ng 
2.17.2
Sat Apr 16 07:25:02 2011: /dev/sda1: clean, 86557/610800 files, 933265/2441216 
blocks
Sat Apr 16 07:25:02 2011: done.
Sat Apr 16 07:25:02 2011: Starting early crypto disks...done.
Sat Apr 16 07:25:02 2011: Cleaning up ifupdown....
Sat Apr 16 07:25:02 2011: Loading kernel modules...done.
Sat Apr 16 07:25:02 2011: Starting remaining crypto disks...done.
Sat Apr 16 07:25:02 2011: Activating lvm and md swap...done.
Sat Apr 16 07:25:02 2011: Checking file systems...fsck from util-linux-ng 2.17.2
Sat Apr 16 07:25:02 2011: /dev/sda6: clean, 252123/4096000 files, 
7857966/16381696 blocks (check in 2 mounts)
Sat Apr 16 07:25:02 2011: done.
Sat Apr 16 07:25:02 2011: Setting up networking....
Sat Apr 16 07:25:02 2011: Mounting local filesystems...done.
Sat Apr 16 07:25:02 2011: Activating swapfile swap...done.
Sat Apr 16 07:25:02 2011: Cleaning up temporary files....
Sat Apr 16 07:25:02 2011: Setting kernel variables ...done.
Sat Apr 16 07:25:02 2011: Configuring network interfaces...resolvconf: Error: 
/etc/resolvconf/run/interface is not a directory
Sat Apr 16 07:25:02 2011: run-parts: /etc/network/if-up.d/000resolvconf exited 
with return code 1
Sat Apr 16 07:25:03 2011: resolvconf: Error: /etc/resolvconf/run/interface is 
not a directory
Sat Apr 16 07:25:03 2011: run-parts: /etc/network/if-up.d/000resolvconf exited 
with return code 1
Sat Apr 16 07:25:03 2011: grep: /etc/resolv.conf: No such file or directory
Sat Apr 16 07:25:03 2011: SIOCSIFADDR: No such device
Sat Apr 16 07:25:03 2011: n900: ERROR while getting interface flags: No such 
device
Sat Apr 16 07:25:03 2011: SIOCSIFNETMASK: No such device
Sat Apr 16 07:25:03 2011: n900: ERROR while getting interface flags: No such 
device
Sat Apr 16 07:25:03 2011: Failed to bring up n900.
Sat Apr 16 07:25:03 2011: done.
Sat Apr 16 07:25:03 2011: Starting portmap daemon....
Sat Apr 16 07:25:03 2011: Starting NFS common utilities: statd.
Sat Apr 16 07:25:03 2011: Cleaning up temporary files....
Sat Apr 16 07:25:03 2011: Setting console screen modes.
Sat Apr 16 07:25:03 2011: ^[]R^[[9;30]^[[14;30]Skipping font and keymap setup 
(handled by console-setup).
Sat Apr 16 07:25:03 2011: Setting up console font and keymap...done.
Sat Apr 16 07:25:03 2011: Setting up ALSA...done.
Sat Apr 16 07:25:03 2011: Setting sensors limits.
Sat Apr 16 07:25:03 2011: Setting up resolvconf...done.
Sat Apr 16 07:25:03 2011: INIT: Entering runlevel: 2
Sat Apr 16 07:25:03 2011: Starting portmap daemon...Already running..
Sat Apr 16 07:25:03 2011: Starting NFS common utilities: statd.
Sat Apr 16 07:25:03 2011: Starting acpi_fakekey daemon...done.
Sat Apr 16 07:25:04 2011: Enabling additional executable binary formats: 
binfmt-support.
Sat Apr 16 07:25:04 2011: Starting polipo: polipo.
Sat Apr 16 07:25:05 2011: Starting enhanced syslogd: rsyslogd.
Sat Apr 16 07:25:05 2011: Starting web server: apache2apache2: Could not 
reliably determine the server's fully qualified domain name, using 127.0.0.1 
for ServerName
Sat Apr 16 07:25:05 2011: .
Sat Apr 16 07:25:05 2011: Checking battery state...done.
Sat Apr 16 07:25:05 2011: Starting ACPI services....
Sat Apr 16 07:25:05 2011: Starting anac(h)ronistic cron: anacron.
Sat Apr 16 07:25:05 2011: Starting deferred execution scheduler: atd.
Sat Apr 16 07:25:05 2011: Starting periodic command scheduler: cron.
Sat Apr 16 07:25:05 2011: Starting system message bus: dbus.
Sat Apr 16 07:25:05 2011: Starting DenyHosts: denyhosts.
Sat Apr 16 07:25:05 2011: Not starting internet superserver: no services 
enabled. ... ^[[33m(warning).^[[39;49m
Sat Apr 16 07:25:05 2011: Starting kerneloops:
Sat Apr 16 07:25:05 2011: Loading cpufreq kernel modules...done (acpi-cpufreq).
Sat Apr 16 07:25:05 2011: Starting PostgreSQL 8.4 database server: main.
Sat Apr 16 07:25:09 2011: Starting OpenBSD Secure Shell server: sshd.
Sat Apr 16 07:25:09 2011: Raising maximum number of filedescriptors (ulimit -n) 
to 32768.
Sat Apr 16 07:25:09 2011: Starting tor daemon: tor...
Sat Apr 16 07:25:09 2011: Apr 16 07:25:09.100 [notice] Tor v0.2.1.29 
(r318f470bc5f2ad43). This is experimental software. Do not rely on it for 
strong anonymity. (Running on Linux i686)
Sat Apr 16 07:25:09 2011: Apr 16 07:25:09.101 [notice] Initialized libevent 
version 1.4.13-stable using method epoll. Good.
Sat Apr 16 07:25:09 2011: Apr 16 07:25:09.102 [notice] Opening Socks listener 
on 127.0.0.1:9050
Sat Apr 16 07:25:09 2011: done.
Sat Apr 16 07:25:09 2011: Starting VirtualBox kernel modules:done..
Sat Apr 16 07:25:09 2011: Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Sat Apr 16 07:25:09 2011: Starting bluetooth: bluetoothd.
Sat Apr 16 07:25:09 2011: CPUFreq Utilities: Setting ondemand CPUFreq 
governor...CPU0...CPU1...done.
Sat Apr 16 07:25:09 2011: Starting MTA: exim4.
Sat Apr 16 07:25:10 2011: ALERT: exim paniclog /var/log/exim4/paniclog has 
non-zero size, mail system possibly broken ... ^[[31mfailed!^[[39;49m
Sat Apr 16 07:25:10 2011: Starting Hardware abstraction layer: hald.
Sat Apr 16 07:25:10 2011: Starting Network connection manager: wicd.
Sat Apr 16 07:25:10 2011: Starting virtual private network daemon:.
Sat Apr 16 07:25:10 2011: Starting Common Unix Printing System: cupsd.
Sat Apr 16 07:25:10 2011: Starting GNOME Display Manager: gdm3.
Sat Apr 16 07:25:11 2011: saned disabled; edit /etc/default/saned
Sat Apr 16 07:25:11 2011: Starting NTP server: ntpd.
Sat Apr 16 07:25:11 2011: Starting Samba daemons: nmbd smbd.
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# allow-hotplug eth0
iface eth0 inet static
      address 192.168.0.7
      netmask 255.255.255.0
      gateway 192.168.0.1
      dns-nameservers 192.168.0.1

auto wlan0
iface wlan0 inet static
      address 192.168.0.7
      netmask 255.255.255.0
      gateway 192.168.0.1
      dns-nameservers 192.168.0.1
      dns-search local
      dns-domain local
      wpa-ssid MotoGuzzi
      wpa-psk ----

#iface wlan0 inet dhcp
#      essid Freewave
#     wpa-ssid airaccess
#      essid metalab_802.11g_NOCRYPT            

allow-hotplug n900
auto n900
iface n900 inet static
        address 192.168.2.7
        netmask 255.255.255.0
        up iptables -A POSTROUTING -t nat -s 192.168.2.15/32 -j MASQUERADE
        up echo 1 > /proc/sys/net/ipv4/ip_forward
        down iptables -D POSTROUTING -t nat -s 192.168.2.15/32 -j MASQUERADE
        down echo 0 > /proc/sys/net/ipv4/ip_forward
        gateway 192.168.2.15    
        dns-nameservers 192.168.2.15
ls -l /etc/resolvconf
insgesamt 16
-rw-r--r-- 1 root root  116 13. Aug 2009  interface-order
drwxr-xr-x 2 root root 4096 11. Apr 15:48 resolv.conf.d
lrwxrwxrwx 1 root root   23 11. Apr 15:48 run -> /lib/init/rw/resolvconf
drwxr-xr-x 2 root root 4096 11. Apr 15:48 update.d
drwxr-xr-x 2 root root 4096 28. Feb 16:08 update-libc.d
ls -l /etc/resolvconf/run
lrwxrwxrwx 1 root root 23 11. Apr 15:48 /etc/resolvconf/run -> 
/lib/init/rw/resolvconf
ls -l /etc/resolvconf/run/interface
insgesamt 0
ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 31 11. Apr 15:48 /etc/resolv.conf -> 
/etc/resolvconf/run/resolv.conf
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
ls -l /etc/resolvconf
insgesamt 16
-rw-r--r-- 1 root root  116 13. Aug 2009  interface-order
drwxr-xr-x 2 root root 4096 11. Apr 15:48 resolv.conf.d
lrwxrwxrwx 1 root root   23 11. Apr 15:48 run -> /lib/init/rw/resolvconf
drwxr-xr-x 2 root root 4096 11. Apr 15:48 update.d
drwxr-xr-x 2 root root 4096 28. Feb 16:08 update-libc.d
ls -l /etc/resolvconf/run
lrwxrwxrwx 1 root root 23 11. Apr 15:48 /etc/resolvconf/run -> 
/lib/init/rw/resolvconf
ls -l /etc/resolvconf/run/interface
insgesamt 4
-rw-r--r-- 1 root root 49 16. Apr 06:53 wlan0.inet
ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 31 11. Apr 15:48 /etc/resolv.conf -> 
/etc/resolvconf/run/resolv.conf
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.1
search local

--- End Message ---
--- Begin Message ---
[2019-07-18 20:08] Jesse Smith <[email protected]>
> On Sun, 17 Apr 2011 20:09:40 +0200 Thomas Hood wrote:
> > I have just reassigned this report from resolvconf to
> > insserv because I believe that the insserv maintainers
> > will have more insight into the problem than I have.
> >
> > Here is a summary of what we have found out, as
> > described earlier in the report's message log.
> >
> > Resolvconf was misbehaving on the submitter's two fresh
> > squeeze machines. This was because resolvconf's initscript
> > had been installed in rcS.d at the traditional sequence
> > number S38 rather than at the appropriate sequence number
> > for the submitter's systems, S13. This was because,
> > although the submitter's systems had evidently been
> > subjected to boot sequence reordering by (I presume)
> > insserv, the /etc/init.d/.legacy-bootordering flag file was
> > still present on his systems.
> >
> > This incongruous situation --- reordered boot sequence, but
> > legacy flag file present --- may have resulted from the
> > presence of initscripts on the system lacking LSB headers.
> > --
> > Thomas Hood
>
>
> This is an interesting bug. Though I'm not sure if it is still a
> problem. As far as I know, current versions of update-rc.d and insserv
> do not check for the ".legacy-bootordering" file flag (or create or
> remove it). I could be mistaken, but I think this was either resolved
> quietly in the past, or is outside our scope. I tried running the latest
> insserv with and without /etc/init.d/.legacy-bootordering in place and
> didn't encounter differences in behaviour.
>
> I think we can probably mark this one as closed unless someone comes up
> with a way insserv is misbehaving in this situation.

Agreed.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

--- End Message ---

Reply via email to