RE: save_all.sh failers on new node
Has everbody forgotten that Foxwatch comms modules could be CP40 these days. Regds Graham Heath EMEA TAC/ Uk. Service +44 1293 406508 +44 1293 417726 FAX -Original Message- From: Ron Deen [mailto:[EMAIL PROTECTED]] Sent: 03 May 2001 18:17 To: Foxboro DCS Mail List Subject: Re: save_all.sh failers on new node Hi Stan, Wat type of module is the FoxWatch module? I would not expect a comms processor to be in /etc/cplns on the system. (FOXWATCH is usually a COMM10 and does not contain a control database) Was the system configuration passed through all stations? (just to sync the system files like /etc/cplns, /etc/aplns, the hosts table, System Monitor files and the like, on all of them). I do not have an Allen-Bradly station at hand and of course the thing you cannot test will fail! Can it be CSA died on you? I will have to check tomorrow since I don't have a lab at home, sorry. The log will be of some help. Ron Deen@home Stan Brown wrote: One of the other groups here, has just put in a new Foxboro node, and I was seting up save_all.sh to autobackup the control config's for them. However, much to my suprise it failed to bacxkup the AB integrator, and FoxWatch modules on that node. Her's the log: Save-all for all stations in /etc/cplns selected Stations selected for save_all: Station Host name CP0101 AW0101 CP0102 AW0101 AB0101 AW0101 FOXW01 AW0101 Checking directories... Creating directory /opt/SAVEALLS Creating directory /opt/SAVEALLS/backup Creating directory for CP0101... Creating directory for CP0102... Creating directory for AB0101... Creating directory for FOXW01... All directories OK. Checking for available diskspace Available space on system: 12910445 Space required on system: 8000 Enough space available, continuing... # # Automatic save-all procedure started # Date: Thu May 3 07:58:48 GMT 2001 # Started on: AW0101 # Save-all Location: /opt/SAVEALLS # Backup location:/opt/SAVEALLS/backup # # # Save_all starting for: CP0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 07:58:48 GMT 2001 --- upload and checkpoint CP0101 DONE 1 OPEN CP0101!: Thu May 3 07:58:48 2001 DONE 2 UPLOAD CP0101!: Thu May 3 08:30:25 2001 DONE 3 SHRINK CP0101!: Thu May 3 08:30:27 2001 DONE 4 CHECKPOINT CP0101!: Thu May 3 08:32:57 2001 DONE 5 CLOSE CP0101!: Thu May 3 08:32:57 2001 DONE 6 EXIT CP0101!: Thu May 3 08:32:57 2001 upload/checkpoint Complete Save_all for CP0101 started Save-all for CP0101 successfully completed. # # Save_all starting for: CP0102 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:33:22 GMT 2001 --- upload and checkpoint CP0102 DONE 1 OPEN CP0102!: Thu May 3 08:33:22 2001 DONE 2 UPLOAD CP0102!: Thu May 3 08:51:03 2001 DONE 3 SHRINK CP0102!: Thu May 3 08:51:04 2001 DONE 4 CHECKPOINT CP0102!: Thu May 3 08:52:12 2001 DONE 5 CLOSE CP0102!: Thu May 3 08:52:12 2001 DONE 6 EXIT CP0102!: Thu May 3 08:52:12 2001 upload/checkpoint Complete Save_all for CP0102 started Save-all for CP0102 successfully completed. # # Save_all starting for: AB0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:52:33 GMT 2001 --- upload and checkpoint AB0101 DONE 1 OPEN AB0101!: Thu May 3 08:52:33 2001 DONE 2 UPLOAD AB0101!: Thu May 3 09:16:33 2001 DONE 3 SHRINK AB0101!: Thu May 3 09:16:34 2001 DONE 4 CHECKPOINT AB0101!: Thu May 3 09:19:49 2001 DONE 5 CLOSE AB0101!: Thu May 3 09:19:49 2001 DONE 6 EXIT AB0101!: Thu May 3 09:19:49 2001 upload/checkpoint Complete Save_all for AB0101 started There were errors for AB0101. FAIL 1 open AB0101!: Thu May 3 09:19:50 2001 -14 ICCopen error: class= 1 error= 0 text= icConnectCp: icCpConnect problem # # Save_all starting for: FOXW01 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 09:19:58 GMT 2001 --- upload and checkpoint FOXW01 FAIL 1 OPEN FOXW01!: Thu May 3 09:19:58 2001 -14 ICCopen error: class= 1 error= 0 text= icConnectCp: icCpConnect problem DONE 6 EXIT FOXW01!: Thu May 3 09:19:58 2001 upload/checkpoint Complete Save_all for FOXW01
RE: AIM AT extraction
The I/A Series Report Package extracts data from the Historian (AIM* or Legacy)and publishes the results in MS Excel and HTML formats. The Data extraction (Reports) can be scheduled or on demand. The PSS number for the report package is PSS 21S-6C8 B3. Regards, Sylvain Nadeau Systems Integration IT Foxboro Canada Inc. [EMAIL PROTECTED] 514-421-8107 Fax:514-421-8054 -Original Message- From: Stefano Persico [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 03, 2001 6:02 PM To: Foxboro DCS Mail List Subject: AIM AT extraction Hi list is it possible to estract data from AIM*Historian samples and convert them in some easy format ( ASCII ) ??? In other words is it possible to read into an ms office application samples from AIM*AT ?? Thanks --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
RE: save_all.sh failers on new node
From: Deen, Ron [mailto:[EMAIL PROTECTED]] Friday, May 04, 2001 7:28 AM Need to get some info on thet AB station. Has anybody tried to run the save_all util in the /opt/fox/ciocfg/api directory to see what that does??? I have been running automated SaveAll on my one AB station for a couple of years now. No problem. I use my own shell wrapper around /opt/fox/ciocfg/api/save_all but I don't think that makes any difference. Just another data point. Duc -- Duc M. Do Process Control Systems Dow Corning, Carrollton Plant Carrollton, KY, US -Original Message- From: Deen, Ron [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 7:28 AM To: Foxboro DCS Mail List Subject: RE: save_all.sh failers on new node You can only forget what you know... Found out today that FoxWatch does run in CP's also. That leaves the problem that these modules should be removed from /etc/cplns in my opinion, otherwise the system expects these modules to contains a control database. The explains the error from the save_all script, because the ICC is not getting a proper response from the FoxWatch module Need to get some info on thet AB station. Has anybody tried to run the save_all util in the /opt/fox/ciocfg/api directory to see what that does??? Still amazing what I can learn from the list though... Ron Deen -Original Message- From: Heath, Graham [mailto:[EMAIL PROTECTED]] Sent: vrijdag 4 mei 2001 9:30 To: 'Foxboro DCS Mail List' Subject: RE: save_all.sh failers on new node Has everbody forgotten that Foxwatch comms modules could be CP40 these days. Regds Graham Heath EMEA TAC/ Uk. Service +44 1293 406508 +44 1293 417726 FAX -Original Message- From: Ron Deen [mailto:[EMAIL PROTECTED]] Sent: 03 May 2001 18:17 To: Foxboro DCS Mail List Subject: Re: save_all.sh failers on new node Hi Stan, Wat type of module is the FoxWatch module? I would not expect a comms processor to be in /etc/cplns on the system. (FOXWATCH is usually a COMM10 and does not contain a control database) Was the system configuration passed through all stations? (just to sync the system files like /etc/cplns, /etc/aplns, the hosts table, System Monitor files and the like, on all of them). I do not have an Allen-Bradly station at hand and of course the thing you cannot test will fail! Can it be CSA died on you? I will have to check tomorrow since I don't have a lab at home, sorry. The log will be of some help. Ron Deen@home Stan Brown wrote: One of the other groups here, has just put in a new Foxboro node, and I was seting up save_all.sh to autobackup the control config's for them. However, much to my suprise it failed to bacxkup the AB integrator, and FoxWatch modules on that node. Her's the log: Save-all for all stations in /etc/cplns selected Stations selected for save_all: Station Host name CP0101 AW0101 CP0102 AW0101 AB0101 AW0101 FOXW01 AW0101 Checking directories... Creating directory /opt/SAVEALLS Creating directory /opt/SAVEALLS/backup Creating directory for CP0101... Creating directory for CP0102... Creating directory for AB0101... Creating directory for FOXW01... All directories OK. Checking for available diskspace Available space on system: 12910445 Space required on system: 8000 Enough space available, continuing... # # Automatic save-all procedure started # Date: Thu May 3 07:58:48 GMT 2001 # Started on: AW0101 # Save-all Location: /opt/SAVEALLS # Backup location:/opt/SAVEALLS/backup # # # Save_all starting for: CP0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 07:58:48 GMT 2001 --- upload and checkpoint CP0101 DONE 1 OPEN CP0101!: Thu May 3 07:58:48 2001 DONE 2 UPLOAD CP0101!: Thu May 3 08:30:25 2001 DONE 3 SHRINK CP0101!: Thu May 3 08:30:27 2001 DONE 4 CHECKPOINT CP0101!: Thu May 3 08:32:57 2001 DONE 5 CLOSE CP0101!: Thu May 3 08:32:57 2001 DONE 6 EXIT CP0101!: Thu May 3 08:32:57 2001 upload/checkpoint Complete Save_all for CP0101 started Save-all for CP0101 successfully completed. # # Save_all starting for: CP0102 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:33:22 GMT 2001 --- upload and checkpoint CP0102 DONE 1 OPEN CP0102!: Thu May 3 08:33:22 2001 DONE 2 UPLOAD CP0102!: Thu May 3 08:51:03 2001 DONE 3 SHRINK CP0102!: Thu May 3 08:51:04 2001 DONE 4 CHECKPOINT CP0102!: Thu May 3 08:52:12 2001 DONE 5 CLOSE CP0102!: Thu May 3 08:52:12 2001 DONE 6 EXIT CP0102!: Thu May 3
RE: save_all.sh failers on new node
You can only forget what you know... Found out today that FoxWatch does run in CP's also. That leaves the problem that these modules should be removed from /etc/cplns in my opinion, otherwise the system expects these modules to contains a control database. The explains the error from the save_all script, because the ICC is not getting a proper response from the FoxWatch module Need to get some info on thet AB station. Has anybody tried to run the save_all util in the /opt/fox/ciocfg/api directory to see what that does??? Still amazing what I can learn from the list though... Ron Deen -Original Message- From: Heath, Graham [mailto:[EMAIL PROTECTED]] Sent: vrijdag 4 mei 2001 9:30 To: 'Foxboro DCS Mail List' Subject: RE: save_all.sh failers on new node Has everbody forgotten that Foxwatch comms modules could be CP40 these days. Regds Graham Heath EMEA TAC/ Uk. Service +44 1293 406508 +44 1293 417726 FAX -Original Message- From: Ron Deen [mailto:[EMAIL PROTECTED]] Sent: 03 May 2001 18:17 To: Foxboro DCS Mail List Subject: Re: save_all.sh failers on new node Hi Stan, Wat type of module is the FoxWatch module? I would not expect a comms processor to be in /etc/cplns on the system. (FOXWATCH is usually a COMM10 and does not contain a control database) Was the system configuration passed through all stations? (just to sync the system files like /etc/cplns, /etc/aplns, the hosts table, System Monitor files and the like, on all of them). I do not have an Allen-Bradly station at hand and of course the thing you cannot test will fail! Can it be CSA died on you? I will have to check tomorrow since I don't have a lab at home, sorry. The log will be of some help. Ron Deen@home Stan Brown wrote: One of the other groups here, has just put in a new Foxboro node, and I was seting up save_all.sh to autobackup the control config's for them. However, much to my suprise it failed to bacxkup the AB integrator, and FoxWatch modules on that node. Her's the log: Save-all for all stations in /etc/cplns selected Stations selected for save_all: Station Host name CP0101 AW0101 CP0102 AW0101 AB0101 AW0101 FOXW01 AW0101 Checking directories... Creating directory /opt/SAVEALLS Creating directory /opt/SAVEALLS/backup Creating directory for CP0101... Creating directory for CP0102... Creating directory for AB0101... Creating directory for FOXW01... All directories OK. Checking for available diskspace Available space on system: 12910445 Space required on system: 8000 Enough space available, continuing... # # Automatic save-all procedure started # Date: Thu May 3 07:58:48 GMT 2001 # Started on: AW0101 # Save-all Location: /opt/SAVEALLS # Backup location:/opt/SAVEALLS/backup # # # Save_all starting for: CP0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 07:58:48 GMT 2001 --- upload and checkpoint CP0101 DONE 1 OPEN CP0101!: Thu May 3 07:58:48 2001 DONE 2 UPLOAD CP0101!: Thu May 3 08:30:25 2001 DONE 3 SHRINK CP0101!: Thu May 3 08:30:27 2001 DONE 4 CHECKPOINT CP0101!: Thu May 3 08:32:57 2001 DONE 5 CLOSE CP0101!: Thu May 3 08:32:57 2001 DONE 6 EXIT CP0101!: Thu May 3 08:32:57 2001 upload/checkpoint Complete Save_all for CP0101 started Save-all for CP0101 successfully completed. # # Save_all starting for: CP0102 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:33:22 GMT 2001 --- upload and checkpoint CP0102 DONE 1 OPEN CP0102!: Thu May 3 08:33:22 2001 DONE 2 UPLOAD CP0102!: Thu May 3 08:51:03 2001 DONE 3 SHRINK CP0102!: Thu May 3 08:51:04 2001 DONE 4 CHECKPOINT CP0102!: Thu May 3 08:52:12 2001 DONE 5 CLOSE CP0102!: Thu May 3 08:52:12 2001 DONE 6 EXIT CP0102!: Thu May 3 08:52:12 2001 upload/checkpoint Complete Save_all for CP0102 started Save-all for CP0102 successfully completed. # # Save_all starting for: AB0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:52:33 GMT 2001 --- upload and checkpoint AB0101 DONE 1 OPEN AB0101!: Thu May 3 08:52:33 2001 DONE 2 UPLOAD AB0101!: Thu May 3 09:16:33 2001 DONE 3 SHRINK AB0101!: Thu May 3 09:16:34 2001 DONE 4 CHECKPOINT AB0101!: Thu May 3 09:19:49 2001 DONE 5 CLOSE AB0101!: Thu May 3 09:19:49 2001 DONE 6 EXIT AB0101!: Thu May
RE: Speaking of Save_All
I suspected as much. Is there anything special about savealls that span more than one disk? just copy the directories to multiple disks however they may fit? -Original Message- From: David Johnson [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 7:45 AM To: Foxboro DCS Mail List Subject: Re: Speaking of Save_All Bo, You should be able to do a cp -r on the directory that you put the save-all in. If the save_all command for CP3001 was: save_all CP3001 /tmp/CP3001 Insert a BLANK FORMATTED Solaris diskette Mount it on /f0 cp -r /tmp/CP3001/* /f0 and that should do it. David --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
Speaking of Save_All
I can't seem to locate the helpful hint that describes how to put these ICC API created save alls that are in a file on the hard disk onto a loadable diskette. Anyone know where that is? --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
RE: save_all.sh failers on new node
the save_all.sh script is a BIG wrapper around the /opt/fox/ciocfg/api/save_all thing. The bottom line is : if that one works, so should the save_all.sh script. The one we send to Cassandra has some (we think) nice options but that's just me trying to sell our own script. Thanks for the response. Ron Deen -Original Message- From: Joe Gale (MP) [mailto:[EMAIL PROTECTED]] Sent: vrijdag 4 mei 2001 14:22 To: 'Foxboro DCS Mail List' Subject: RE: save_all.sh failers on new node We have 13 AB stations and 1 AB Gateway on our site. I have a auto saveall script that is working on these modules, I am not sure if it is doing the exact same thing as your save_all.sh script though. Not much help other then to say that we have gotten this to work. Joe -Original Message- From: Deen, Ron [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 6:28 AM To: Foxboro DCS Mail List Subject: RE: save_all.sh failers on new node You can only forget what you know... Found out today that FoxWatch does run in CP's also. That leaves the problem that these modules should be removed from /etc/cplns in my opinion, otherwise the system expects these modules to contains a control database. The explains the error from the save_all script, because the ICC is not getting a proper response from the FoxWatch module Need to get some info on thet AB station. Has anybody tried to run the save_all util in the /opt/fox/ciocfg/api directory to see what that does??? Still amazing what I can learn from the list though... Ron Deen -Original Message- From: Heath, Graham [mailto:[EMAIL PROTECTED]] Sent: vrijdag 4 mei 2001 9:30 To: 'Foxboro DCS Mail List' Subject: RE: save_all.sh failers on new node Has everbody forgotten that Foxwatch comms modules could be CP40 these days. Regds Graham Heath EMEA TAC/ Uk. Service +44 1293 406508 +44 1293 417726 FAX -Original Message- From: Ron Deen [mailto:[EMAIL PROTECTED]] Sent: 03 May 2001 18:17 To: Foxboro DCS Mail List Subject: Re: save_all.sh failers on new node Hi Stan, Wat type of module is the FoxWatch module? I would not expect a comms processor to be in /etc/cplns on the system. (FOXWATCH is usually a COMM10 and does not contain a control database) Was the system configuration passed through all stations? (just to sync the system files like /etc/cplns, /etc/aplns, the hosts table, System Monitor files and the like, on all of them). I do not have an Allen-Bradly station at hand and of course the thing you cannot test will fail! Can it be CSA died on you? I will have to check tomorrow since I don't have a lab at home, sorry. The log will be of some help. Ron Deen@home Stan Brown wrote: One of the other groups here, has just put in a new Foxboro node, and I was seting up save_all.sh to autobackup the control config's for them. However, much to my suprise it failed to bacxkup the AB integrator, and FoxWatch modules on that node. Her's the log: Save-all for all stations in /etc/cplns selected Stations selected for save_all: Station Host name CP0101 AW0101 CP0102 AW0101 AB0101 AW0101 FOXW01 AW0101 Checking directories... Creating directory /opt/SAVEALLS Creating directory /opt/SAVEALLS/backup Creating directory for CP0101... Creating directory for CP0102... Creating directory for AB0101... Creating directory for FOXW01... All directories OK. Checking for available diskspace Available space on system: 12910445 Space required on system: 8000 Enough space available, continuing... # # Automatic save-all procedure started # Date: Thu May 3 07:58:48 GMT 2001 # Started on: AW0101 # Save-all Location: /opt/SAVEALLS # Backup location:/opt/SAVEALLS/backup # # # Save_all starting for: CP0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 07:58:48 GMT 2001 --- upload and checkpoint CP0101 DONE 1 OPEN CP0101!: Thu May 3 07:58:48 2001 DONE 2 UPLOAD CP0101!: Thu May 3 08:30:25 2001 DONE 3 SHRINK CP0101!: Thu May 3 08:30:27 2001 DONE 4 CHECKPOINT CP0101!: Thu May 3 08:32:57 2001 DONE 5 CLOSE CP0101!: Thu May 3 08:32:57 2001 DONE 6 EXIT CP0101!: Thu May 3 08:32:57 2001 upload/checkpoint Complete Save_all for CP0101 started Save-all for CP0101 successfully completed. # # Save_all starting for: CP0102 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:33:22 GMT 2001 --- upload and checkpoint CP0102 DONE 1 OPEN CP0102!: Thu May 3 08:33:22 2001 DONE 2 UPLOAD CP0102!: Thu May
Re: Speaking of Save_All
I'm not sure about the name, but I think on the harddrive in the save_all directory, there's a file named compound.dir which contains the names (in order) of the compounds to be loaded. This is the same sequence as they appear in in ICC. Follow that list to create the diskette and you will be assured that the compounds will be loaded in the same sequence. I believe ECB's still go first, put these on the first diskette. Load_all's can be performed from the commandline too. Go to /opt/fox/ciocfg/api and run load_allcr for some usage info. The command take two arguments: station and location/station or the other way around, I can never remember. I could have them mixed up but I think: load_all letterbug location_of_savealls/letterbug comes close. You should not need it too often I hope... Regards Ron Deen@home Stear, Bo wrote: I suspected as much. Is there anything special about savealls that span more than one disk? just copy the directories to multiple disks however they may fit? -Original Message- From: David Johnson [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 7:45 AM To: Foxboro DCS Mail List Subject: Re: Speaking of Save_All Bo, You should be able to do a cp -r on the directory that you put the save-all in. If the save_all command for CP3001 was: save_all CP3001 /tmp/CP3001 Insert a BLANK FORMATTED Solaris diskette Mount it on /f0 cp -r /tmp/CP3001/* /f0 and that should do it. David --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: /etc/wplns and /etc/aplns
On Thu May 3 13:41:12 2001 Ron Deen wrote... The /etc/wplns file contains the logical names of the WP's on your system. The /etc/aplns contains (you might have guessed) the logical names of the AP in you system. If you have only AP's and WP's you would normally use the letterbug as the logical name. If you have AW's you have a problem: the AW containss a logical AP AND a logical WP and only one can be be letterbug name. This is why you may see strange names on you system. Some time you can have a letterbug AW0101 which will have aplns: AW0101 and wplns: AWWP01 for instance. Ah, I went and looked on another system with an AW, I see what you are tlaking about. However when I worked on the script i _ASSUMED_ that this name was generated autmaticly, and would follow a pattern, silly me :-( Thanks. -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited. --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
