Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Dec 2013 15:49:42 GMT
From:      Maciej Sobczak <prog@msobczak.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   bin/184999: devd: Cannot parse /etc/devd.conf at line 202
Message-ID:  <201312191549.rBJFngQw049313@oldred.freebsd.org>
Resent-Message-ID: <201312191550.rBJFo1VG023877@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         184999
>Category:       bin
>Synopsis:       devd: Cannot parse /etc/devd.conf at line 202
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Dec 19 15:50:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Maciej Sobczak
>Release:        10.0 RC2
>Organization:
>Environment:
System installed in VirtualBox, uname -a:

FreeBSD maciej-FreeBSD 10.0-RC2 FreeBSD 10.0-RC2 #0 r259404: Sun Dec 15 11:45:13 UTC 2013     root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386

>Description:
i386 system (10.0 RC2) was installed in the VirtualBox and from the first boot after installation there is a message as in synopsis.
Interestingly, when the /etc/devd.conf file is viewed with less, no problem can be seen, but vi shows a very long series of ^@ special characters from the middle of the 202 line.

Problem is repeatable.

It looks like there is some problem with text parsing.
The system does not work properly due to this (no network, for example).

Note a similar discussion:

http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044816.html

Note: 9.2-RELEASE (i386) works fine in the same environment.

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201312191549.rBJFngQw049313>