emmonsl@athena.ecs.csus.edu (L. Scott Emmons) (04/30/91)
I've had my 3000UX for a couple of weeks now, and have been attempting to develop some socket stuff on it, and have run into a few problems. Following is my list of problems (not all related to sockets) which I have run into on the 3000UX. If anyone can offer ideas/hints/etc I would appreciate it greatly. Not all of these problems are due to the 3000UX, I'm sure nearly all (if not all) are do to "user error". One of the most annoying problems occurs when I close down a socket and the processes associated with that socket die off. When I try to reuse the socket I get "address already in use" for ~15 seconds. I found some info (in streamio(7)) which seems to indicate that the STREAMS implementation keeps an address blocked for this period of time. I attempted to use the I_SETCLITIME ioctl() to set this to the minimum value (16ms) yet this does not work...the socket still doesn't recycle for 15 seconds. Any ideas? Is this something in the STREAMS implementation which does not exist in the BSD one? I've never run into this under BSD. I've found that /usr/ucb must be early in my path in order for gcc to work correctly, and I have to explicitly name the libraries I need (-l socket & -l ucb). The explicit naming is perhaps something with Sys-V (again, the bulk of my programming has been on BSD-derived systems). Although the above works, ld complains: "ld : /usr/lib/libsocket.so: warning: attempted multiple inclusion of file". I'm using /usr/ucb/ld, if it matters... Sdb seems to be unable to find my source file, and it's in the current working directory. Yes, compiled with -g option. Anyone build gdb for 3000UX? Will the lack of job control in csh under X be fixed? Rather annoying. I get i/o errors when I 'q' out of more when viewing man pages. Maybe it has something to do with uncompress not being happy about having the pipeline shutdown abruptly? No man pages on devices! What's the difference between fd0 and fd0f, anyway? Are there plans to fix the floppy device driver and make it compatable with anything besides other Amiga's? I've tried dd/tar/cpio on floppies to and from sun's and at&t 386 unix boxes...the amiga is not compatable with either of them...bleagh! Anyone built mtools and get it to work? Will there be plans to ship standard, printed manual pages? Online manual is great, but I like 'em on paper too. The only ones that come with the amiga are introduction-level. Will the 'sysadm' tools be fixed so that the screen picture of function keys will match the physical location of them? /usr/X/lib/fonts/75dpi is in my path, xlsfonts shows them (in a long format), but xset won't find them. Do some lists need to be fixed somewhere? And lastly, finally, can the console be set to have a particular screen size, color, and font, like the rest of the virtual screens can? I can't seem to make it work. Again, thanks for any help, I appreciate it greatly!! L. Scott Emmons --------------- emmons@csus.csus.edu <or> ...[ucbvax]!ucdavis!csus!emmons Packet: kc6nfp@kg6xx.#nocal.ca.usa.na
emmonsl@athena.ecs.csus.edu (L. Scott Emmons) (04/30/91)
In some article I wrote: > [deleted] >One of the most annoying problems occurs when I close down a socket and the >processes associated with that socket die off... > [deleted] Well, once again I find that the easiest way to solve a problem is to post it to everyone on the planet; and then, invariably, I solve it myself within an hour of the post...The problem had to do with phantom data hanging around in the socket queue; nothing a while(read(s,&c,1)); couldn't fix... Since my assumption about the use of STREAMS to implement sockets seems to be incorrect, can anyone tell me what STREAMS is for? Is it just a 'brand name' of TCP/IP? Thanks again! L. Scott Emmons --------------- emmons@csus.csus.edu <or> ...[ucbvax]!ucdavis!csus!emmons Packet: kc6nfp@kg6xx.#nocal.ca.usa.na
buck@amix.commodore.com (Richard Buck) (05/10/91)
I can answer a few, but not all, of your questions. emmonsl@athena.ecs.csus.edu (L. Scott Emmons) writes: > Sdb seems to be unable to find my source file, and it's in the current > working directory. Yes, compiled with -g option. Anyone build gdb for > 3000UX? Working on it, as well as improved versions of adb and sdb for 2.0. > > I get i/o errors when I 'q' out of more when viewing man pages. Maybe it > has something to do with uncompress not being happy about having the > pipeline shutdown abruptly? No, it's a "feature" of the cat command. No longer used and no longer a problem in version 2.0. > > Will there be plans to ship standard, printed manual pages? Online manual > is great, but I like 'em on paper too. The only ones that come with the > amiga are introduction-level. We recommend that people buy any printed UNIX Press manuals they want. Many other Release 4 vendors are starting to pursue this path, and USL is pursuing an approach that will allow all vendors to ship a subset of the documentation and refer buyers to the generic UNIX Press set. The reason is simple: nobody wants to make a customer pay for many printed books they don't need, so we let people choose and pay for only the books they need, from the complete set that UNIX Press prints and sells through bookstores. Amiga 3000UX systems are shipped with a discount order form from UNIX Press, so you can order any books you want. Our choice for supplemental books was to address what you call the "introduction-level" users, since these are the people least likely to be able to use regular USL manuals and man pages. We will be supplementing this introductory set with an advanced networking and administration guide soon, but we will never try to replace or compete with the complete programmer's documentation from USL. > > Will the 'sysadm' tools be fixed so that the screen picture of function > keys will match the physical location of them? Sort of. > > And lastly, finally, can the console be set to have a particular screen > size, color, and font, like the rest of the virtual screens can? I can't > seem to make it work. For version 1.1, you can permanently set the color and font, not the resolution, but in a different way than the other screens. In 2.0, the same conditions apply, but one screen characteristics file handles all screens, including the console, the same way. For 1.1, put a line like the following near the top of /etc/inittab. This simply applies the color command to the console at startup. S2::sysinit:/usr/amiga/bin/color -bc 037 -fc fcb < /dev/console > /dev/console You can do the same thing for fonts with an sioc setfont command. >
buck@amix.commodore.com (Richard Buck) (05/10/91)
emmonsl@athena.ecs.csus.edu (L. Scott Emmons) writes: > Since my assumption about the use of STREAMS to implement sockets seems to be > incorrect, can anyone tell me what STREAMS is for? Is it just a 'brand name' > of TCP/IP? In the latest issue of Tech Notes (second issue, mailed a couple weeks ago), Mike Ditto writes a neat two-page article describing the purpose and use of STREAMS. He's also got a troff version of this article, with graphics, which maybe he'll send to people if they ask nicely. > > L. Scott Emmons > --------------- -- "Klaatu barada nicto" Richard Buck, (215) 344-3019, buck@amix.commodore.com (4/91)