Poštni seznam arhiviranih sporo?il

Od:	Christian Langanke <os2-wireless_users@2rosenthals.com>	Glava Izvorno E-sporo?ilo
Pošiljalec:	os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Zadeva:	[OS2Wireless] XWLAN options - enhancement requests
Datum:	Thu, 21 Oct 2004 23:18:00 +0200
Za:	os2-wireless_users@2rosenthals.com

Lewis G Rosenthal wrote: Christian, getting back to the scripts idea, I think it would be nice for each profile to have pre- and post- connection options. Scripts could be added in here. For example, I run Squid locally, which helps keep my Mozilla cache very small. However, when I am using any connection profile besides my default one (i.e., when XWLAN is taking some time to scan connections), Squid, which starts from my Startup folder, shuts down. This is because it can't validate my DNS settings. Yes, I know I can override this test in squid.conf, but the idea is that it would be nice for me to be able to specify a particular script or command to run after a valid DHCP lease is obtained (maybe I want to bring up Mozilla Mail right away, instead of clicking on it). Good point ! BTW; for your squid problem I would use a local DNS with forwarders for that, AFAIK on hobbes there are some bind versions (bind == DNS server) around. But if you never configured a DNS server, I am sure you surely want to avoid this. Beside that I see your point. And again, this would allow for those who need or want connection scripts to change interfaces or override some DHCP-supplied parameters (DNS, etc.). At least ovverides of DHCP options should should normally be solved with DHCP methods, just disable the option in the DHCPCD.CFG. But I see a problem where one would want to use different DHCP configurations for different connections. Unfortunately it seems not to be possible to use different dhcpcd.cfg files, AFAIK one cannot specify a separeate config file :-( And I don't dare to set ETC to something different to launch a DHCPCD with a separate config - you never know what will happen (not work) then. Again, the implementation of IBM is narrow-minded and outdated (same with allowing DHCP only for one interface at a time). Including connect and disconnect scripts will be quite a major change and take some time. Moreover, it may make sense to use REXX extension scripts as a script solution. XWLAN would create an own REXX environment (e.g. "XWLAN" or "XWL") so that REXX scripts can easily access internal XWLAN variables, like querying the settings of the current profile etc. From those application specific REXX files, of course, OS/2 commands can still be executed. Beside that, of course plain CMD files could be supported as well, possibly passing XWLAN values as environment variables to the called process. thanx, Christian ------------------------------------------------- Christian Langanke COS2E & CWSE Team OS/2 Ruhr e.V. cla@clanganke.de =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To unsubscribe from this list, send a message to steward@2rosenthals.com with the command "unsubscribe os2-wireless_users" in the body (omit the quotes). For help with other commands, send a message to steward@2rosenthals.com with the command "help" in the body (omit the quotes). This list is hosted by Rosenthal & Rosenthal P.O. Box 281, Deer Park, NY 11729-0281. Non- electronic communications related to content contained in these messages should be directed to the above address. (CAN-SPAM Act of 2003) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Naro?iti: Poro?ilo (Feed), Izvle?ek (Digest), Indeks.
Odjava
E-pošta za mojstra za sezname