-
Re the 2009-06-23 23:30 reply:
Adding the third argument to netsnmp_copy_fd_set_to_large_fd_set() and netsnmp_copy_large_fd_set_to_fd_set() works but as I mentioned this only helps snmp_select_info()/snmp_sess_select_info() but not snmp_read()/snmp_sess_read() which also takes a fd_set, converts it to a large_fd_set, and passes that along to snmp_sess_read2(). A solution to this that just came...
2009-06-24 22:34:20 UTC in net-snmp
-
Although I welcome the ability to handle this better (it took me a while to figure out a memory corruption problem due to trying to fit large fds in a nomral fd_set) this change breaks how large fds must be handled with older versions of net-snmp. As outlined in the original patch ticket (1627049) the solution for using select with large fds is to simply create an extra large fd_set variable...
2009-06-24 05:07:46 UTC in net-snmp
-
marineam committed patchset 24 of module beepfind to the Xmmsfind CVS repository, changing 2 files.
2005-05-14 17:37:25 UTC in Xmmsfind
-
marineam committed patchset 23 of module beepfind to the Xmmsfind CVS repository, changing 10 files.
2005-04-29 03:03:52 UTC in Xmmsfind
-
marineam committed patchset 56 of module xmmsfind to the Xmmsfind CVS repository, changing 2 files.
2005-04-29 02:34:04 UTC in Xmmsfind
-
marineam committed patchset 55 of module xmmsfind to the Xmmsfind CVS repository, changing 1 files.
2005-03-27 00:35:55 UTC in Xmmsfind
-
marineam committed patchset 22 of module beepfind to the Xmmsfind CVS repository, changing 1 files.
2005-03-27 00:35:39 UTC in Xmmsfind
-
The following is marked in the TODO currently:
[ ] Either (A) don't use any global variables or (B) rename all the
global variables with a "webcalendar_" prefix.
(This includes $login, $user and other variables.)
I'm in favor of (A) where ever possible. for example, in my customizations I converted the user_load_variables function into a user_get_info that returns an...
2005-03-02 06:04:28 UTC in WebCalendar
-
In mysql there isn't a hard limit on description size
(or at least none that WebCalendar defines) so there is
no need to truncate event descriptions in
import_handler.php. There may be other parts that have
a hard limit but I have not found them yet. A patch to
remove the truncation in import_handler is attached.
Looking at other sample database tables, some do set
this hard limit...
2005-02-18 21:47:19 UTC in WebCalendar
-
I'll give it a try sometime in the comming week and let you know :-)
2005-01-10 20:10:44 UTC in WebCalendar
