Bug 89435 - service ip netmask of "None" causes "[ip]/None" in /etc/samba/smb.conf.sharename
service ip netmask of "None" causes "[ip]/None" in /etc/samba/smb.conf.sharename
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: clumanager (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Depends On:
  Show dependency treegraph
Reported: 2003-04-22 16:57 EDT by Hardy Merrill
Modified: 2007-11-30 17:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-10-03 11:22:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Hardy Merrill 2003-04-22 16:57:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
Using 'cluadmin' to add a service, you are prompted for ip address and netmask
information.  For 'netmask', you are allowed to specify 'None' - but doing that
causes this to appear in the /etc/samba/smb.conf.sharename file:

  interfaces = [ip]/None

When 'None' is specified as the netmask, the interfaces should look like this:

  interfaces = [ip]

with no '/None' tacked on.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. use cluadmin to add a service
2. add an ip address, and specify 'None' as the netmask
3. observe that the /etc/samba/smb.conf.sharename file ends up with
   an 'interfaces' value that looks like '[ip]/None'.  This is

Actual Results:  When 'None' as specified as the netmask, the
/etc/samba/smb.conf.sharename should end up with an 'interfaces' value like
'[ip]' - with no '/None' tacked on.

Additional info:
Comment 1 Lon Hohberger 2003-04-28 14:19:48 EDT
Fix in CVS pool.  Will be in next erratum.
Comment 2 Suzanne Hillman 2003-10-03 11:22:51 EDT
Since U2 was in May, and the fix was submitted to CVS in late April, I'm going
to guess that this fix was in U2, and close this. If the problem was not
resolved, please reopen.

Note You need to log in before you can comment on or make changes to this bug.