Mike Ramchand wrote: > Brian, > > Two points: > > To run as non-root user, you simply need to create a profile in > /etc/user_attr > > <username>::::type=normal;profiles=Ginetmenu
I know. As I said, I used to be able to do it without a problem. And it helped to do the truss, which had to be done by root to truss across the pfexec. But the inetmenu was still running as me. > > > Given that inetmenu is a script, it simply calls ifconfig, wificonfig, > to do the right thing. It should be possible to figure out at which > point it hangs. I am pretty sure that it is hanging in ifconfig, although the truss does not show it. It is possible (likely) that the truss file is behind because of the hang. The core file shows an ifconfig child process to the inetmenu script. > > P.S. Are you using the latest version of inetmenu? > Does this EVER happen with your ethernet interface? > Which wireless driver are you using? Is it the latest version? I am using version 1.9. I don't think it has ever happened with the ethernet interface. I am using bcmndis. I think I am using ndis wrapper 1.6. Also, when I run inetmenu as route and choose the bcmndis0 interface to configure, I get an error message from the "tr" command. I just noticed that I get some warnings in the messages file: May 24 16:59:13 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0xc0786981 May 24 16:59:13 metatron bcmndis: [ID 975483 kern.notice] ndis_gld_ioctl: unknown cmd 0xc0786981 May 24 16:59:13 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0x40586993 May 24 16:59:13 metatron bcmndis: [ID 975483 kern.notice] ndis_gld_ioctl: unknown cmd 0x40586993 May 24 16:59:13 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0x1004 May 24 16:59:13 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0x1003 May 24 16:59:15 metatron last message repeated 1 time May 24 16:59:15 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0x1004 May 24 16:59:15 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0x1002 May 24 16:59:15 metatron last message repeated 1 time May 24 16:59:15 metatron bcmndis: [ID 428280 kern.notice] in the cfg essid!! May 24 16:59:15 metatron bcmndis: [ID 178118 kern.notice] bssid=utterbacks May 24 16:59:15 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0x1002 May 24 16:59:15 metatron last message repeated 1 time May 24 16:59:15 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0x1003 May 24 16:59:15 metatron bcmndis: [ID 141910 kern.notice] link up May 24 16:59:16 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0x1003 May 24 16:59:16 metatron last message repeated 1 time May 24 16:59:27 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0xffffffff May 24 16:59:27 metatron bcmndis: [ID 975483 kern.notice] ndis_gld_ioctl: unknown cmd 0xffffffff May 24 16:59:30 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0xffffffff May 24 16:59:30 metatron bcmndis: [ID 975483 kern.notice] ndis_gld_ioctl: unknown cmd 0xffffffff May 24 16:59:30 metatron bcmndis: [ID 446631 kern.notice] ndis_gld_ioctl: cmd 0xffffffff May 24 16:59:30 metatron bcmndis: [ID 975483 kern.notice] ndis_gld_ioctl: unknown cmd 0xffffffff However, these message look like they date back to when the bcmndis0 driver was installed, before I had the problem. Any suggestions about how to figure out what ifconfig was doing when the thing hung? -- blu Rose are #FF0000, Violets are #0000FF. All my base are belong to you. ---------------------------------------------------------------------- Brian Utterback - OP/N1 RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
