document some limits of "group-name"; from Steffen Daode Nurpmeso

ok henning

1 files changed, 5 insertions, 4 deletions

diff --git a/sbin/ifconfig/ifconfig.8 b/sbin/ifconfig/ifconfig.8
index e036b36471d..751a788ab0b 100644
--- a/sbin/ifconfig/ifconfig.8
+++ b/sbin/ifconfig/ifconfig.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ifconfig.8,v 1.219 2011/07/09 08:44:54 jmc Exp $
+.\"	$OpenBSD: ifconfig.8,v 1.220 2011/10/25 11:39:07 jmc Exp $
 .\"	$NetBSD: ifconfig.8,v 1.11 1996/01/04 21:27:29 pk Exp $
 .\"     $FreeBSD: ifconfig.8,v 1.16 1998/02/01 07:03:29 steve Exp $
 .\"
@@ -31,7 +31,7 @@
 .\"
 .\"     @(#)ifconfig.8	8.4 (Berkeley) 6/1/94
 .\"
-.Dd $Mdocdate: July 9 2011 $
+.Dd $Mdocdate: October 25 2011 $
 .Dt IFCONFIG 8
 .Os
 .Sh NAME
@@ -206,10 +206,11 @@ This action automatically disables routes using the interface.
 .It Cm group Ar group-name
 Assign the interface to a
 .Dq group .
+.Ar group-name
+may not be longer than 15 characters and must not end with a digit.
 Any interface can be in multiple groups.
 .Pp
-For instance, such a group could be used to create a hardware
-independent
+For instance, a group could be used to create a hardware independent
 .Xr pf 4
 ruleset (i.e. not one based on the names of NICs) using
 existing (egress, carp, etc.) or user-defined groups.