conf/150599: /etc/rc.d/jail does not set jailname.

[Uffe Jakobsen]

>Number:         150599
>Category:       conf
>Synopsis:       /etc/rc.d/jail does not set jailname.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Sep 15 18:40:01 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator:     Uffe Jakobsen
>Release:        FreeBSD 8.1-RELEASE
>Organization:
>Environment:
FreeBSD asp1410 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:55:53 UTC 2010     root at almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

>Description:
/etc/rc.d/jail does not set jailname.

Using FreeBSD 8.1-STABLE I've found that the standard /etc/rc.d/jail script does not create jails with "proper" names.

If you inspect your running jails (the ones started with /etc/rc.jail) with # jls -n you will see that jailname is equal to the jail id (jid)

Now I know that this is not directly a bug - but merely a matter of approach in /etc/rc.d/jail. Jails created without specific/explicit names will get their jid as the jailname by default.

But having "jid" and "jailname" equal each other reduces the usability for utilities like jls and jps that according to their man pages can take either jid or jailname as an argument.

The next question is what the jailname actually should be set to ?

1) should it be the jail "name" as referred to in /etc/rc.conf (eg "xyz" as in "jail_xyz_ip") ?

2) should it be the hostname (jail_xyz_hostname=) ?

3) or should the jailname have a (new) separate attribute in /etc/rc.conf (eg. "jail_xyz_name") ?


>How-To-Repeat:

Create a jail enable it in /etc/rc.conf and let it start through /etc/rc.d/jail


>Fix:

For every jail that is started through /etc/rc.d/jail add the line below into /etc/rc.conf:

jail_xyz_flags="-n somename"



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