[arch-general] Is 'network' daemon needed when using netcfg?
I recently tried netcfg, and have setup automatic connection at boot. However during the startup, it says something like "This functionality is deprecated". In my /etc/rc.conf, I have these for networking:
HOSTNAME="XeCycle" NETWORK_PERSIST="no" NETWORKS=(profile) DAEMONS=(syslog-ng dbus network net-profiles netfs crond sensors \ sshd hddtemp dictd cdemud)
So, should I remove 'network' from the 'DAEMONS'? Thank you. PS. Is the process of starting daemons logged? When I ran into problems about daemons, usually I can't know exactly what had happened, because before I could read the error messages, they disappeared.
On Mon, Jun 27, 2011 at 2:12 PM, XeCycle <xecycle@gmail.com> wrote:
I recently tried netcfg, and have setup automatic connection at boot. However during the startup, it says something like "This functionality is deprecated". In my /etc/rc.conf, I have these for networking:
HOSTNAME="XeCycle" NETWORK_PERSIST="no" NETWORKS=(profile) DAEMONS=(syslog-ng dbus network net-profiles netfs crond sensors \ sshd hddtemp dictd cdemud)
So, should I remove 'network' from the 'DAEMONS'?
Yes, netcfg is a replacement for the network daemon.
PS. Is the process of starting daemons logged? When I ran into problems about daemons, usually I can't know exactly what had happened, because before I could read the error messages, they disappeared.
/var/log/boot.log Cheers, Tom
Tom Gundersen <teg@jklm.no> writes:
On Mon, Jun 27, 2011 at 2:12 PM, XeCycle <xecycle@gmail.com> wrote:
I recently tried netcfg, and have setup automatic connection at boot. However during the startup, it says something like "This functionality is deprecated". In my /etc/rc.conf, I have these for networking:
HOSTNAME="XeCycle" NETWORK_PERSIST="no" NETWORKS=(profile) DAEMONS=(syslog-ng dbus network net-profiles netfs crond sensors \ sshd hddtemp dictd cdemud)
So, should I remove 'network' from the 'DAEMONS'?
Yes, netcfg is a replacement for the network daemon.
Thank you for this.
PS. Is the process of starting daemons logged? When I ran into problems about daemons, usually I can't know exactly what had happened, because before I could read the error messages, they disappeared.
/var/log/boot.log
Thank you. But here I have only /var/log/boot, and it contains many '^[['s --- the ASCII control characters aren't properly stored, I have do to a `sed 's/\^\[/^V<ESC>/g'` to read it. Is this a bug?
Cheers,
Tom
On Mon, Jun 27, 2011 at 2:43 PM, XeCycle <xecycle@gmail.com> wrote:
Tom Gundersen <teg@jklm.no> writes:
On Mon, Jun 27, 2011 at 2:12 PM, XeCycle <xecycle@gmail.com> wrote:
I recently tried netcfg, and have setup automatic connection at boot. However during the startup, it says something like "This functionality is deprecated". In my /etc/rc.conf, I have these for networking:
HOSTNAME="XeCycle" NETWORK_PERSIST="no" NETWORKS=(profile) DAEMONS=(syslog-ng dbus network net-profiles netfs crond sensors \ sshd hddtemp dictd cdemud)
So, should I remove 'network' from the 'DAEMONS'?
Yes, netcfg is a replacement for the network daemon.
Thank you for this.
PS. Is the process of starting daemons logged? When I ran into problems about daemons, usually I can't know exactly what had happened, because before I could read the error messages, they disappeared.
/var/log/boot.log
Thank you. But here I have only /var/log/boot, and it contains many '^[['s --- the ASCII control characters aren't properly stored, I have do to a `sed 's/\^\[/^V<ESC>/g'` to read it. Is this a bug?
That's just the format that bootlogd produces. We have a patch in git to clean it up. I don't know if that patch is perfect though, you could try it out. If you find a way to improve it I'd be happy to merge it. -t
On Mon, Jun 27, 2011 at 7:12 AM, XeCycle <xecycle@gmail.com> wrote:
I recently tried netcfg, and have setup automatic connection at boot. However during the startup, it says something like "This functionality is deprecated". In my /etc/rc.conf, I have these for networking:
HOSTNAME="XeCycle" NETWORK_PERSIST="no" NETWORKS=(profile) DAEMONS=(syslog-ng dbus network net-profiles netfs crond sensors \ sshd hddtemp dictd cdemud)
So, should I remove 'network' from the 'DAEMONS'?
Thank you.
PS. Is the process of starting daemons logged? When I ran into problems about daemons, usually I can't know exactly what had happened, because before I could read the error messages, they disappeared.
Have a look at this page: https://wiki.archlinux.org/index.php/Disable_Clearing_of_Boot_Messages#Have_...
participants (3)
-
Buce
-
Tom Gundersen
-
XeCycle