default to a session cookie instead of setting an explicit timeout, weird timezone...

[freeside.git] / FS / FS / port.pm

diff --git a/FS/FS/port.pm b/FS/FS/port.pm
index 620030a..c26ca85 100644 (file)
--- a/FS/FS/port.pm
+++ b/FS/FS/port.pm
@@ -52,7 +52,7 @@ from FS::Record.  The following fields are currently supported:
 
 =item new HASHREF
 
 
 =item new HASHREF
 

-Creates a new port.  To add the example to the database, see L<"insert">.
+Creates a new port.  To add the port to the database, see L<"insert">.

 
 Note that this stores the hash reference, not a distinct copy of the hash it
 points to.  You can ask the object for a copy with the I<hash> method.
 
 Note that this stores the hash reference, not a distinct copy of the hash it
 points to.  You can ask the object for a copy with the I<hash> method.


@@ -91,7 +91,7 @@ returns the error, otherwise returns false.
 
 =item check
 
 
 =item check
 

-Checks all fields to make sure this is a valid example.  If there is
+Checks all fields to make sure this is a valid port.  If there is

 an error, returns the error, otherwise returns false.  Called by the insert
 and replace methods.
 
 an error, returns the error, otherwise returns false.  Called by the insert
 and replace methods.
 


@@ -131,14 +131,8 @@ sub session {
 
 =back
 
 
 =back
 

-=head1 VERSION
-
-$Id: port.pm,v 1.6 2003-08-05 00:20:45 khoff Exp $
-

 =head1 BUGS
 
 =head1 BUGS
 

-The author forgot to customize this manpage.
-

 The session method won't deal well if you have multiple open sessions on a
 port, for example if your RADIUS server drops B<stop> records.  Suggestions for
 how to deal with this sort of lossage welcome; should we close the session
 The session method won't deal well if you have multiple open sessions on a
 port, for example if your RADIUS server drops B<stop> records.  Suggestions for
 how to deal with this sort of lossage welcome; should we close the session