| Title: | PATHWORKS for OSF/1 |
| Notice: | see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX |
| Moderator: | CPEEDY::LONG |
| Created: | Thu Apr 22 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1874 |
| Total number of notes: | 6870 |
Hi, I have a very strange problem using PW6.1 eco1 or eco2. The customer have a WNT 4.0 Server as PDC. and a PW5.0x on a Digital Unix machine as BDC. Then we configure another Digital Unix 4.0B machine as BDC using PW6.1 eco1 ( eco2 has the same behavior ). During the pwsetup phase we added the computer to the domain without any problem. At this point same of the user are not able to create or directory files on the shares on the PW6.1 server. Working on the other servers shares gives no problem. The shares protection are Full Control for Everyone. They can delete files , append to files but are not able to create any new files or directory. The only way we found to avoid this is to give the admin permission to the users in the pwadmin-user page or to put the user in the Domain Admin group using the WNT usermgr utility ( I think is the same ...). If we create a new user everything works fine without the need of the Admin priviledge ( or the need to put the user in the Domain Admin group ). If we COPY an existing user using the pwadmin utility or the usermgr utility we create a new user with the same problem and we need to put the user in the Domain Admin group to allow the user to write on the shares. The only info I can add is that the customer is using the mapuser utility on the PW6.1 server to map the LM user to an Digital Unix user. And last ... the mapuser utility on the PW6.1 server gives a lot of error message that a can't post here now. Can someone help me explaining what can be wrong in the existing user or what can i do to find what are going wrong ? Thanks a lot Gabriele Casarotti [Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1775.1 | still in trouble .. more info | NETRIX::"[email protected]" | Gabriele Casarotti | Mon Mar 10 1997 03:58 | 59 |
I've been on the customer site again. In previous notes there are a couple of mistake but I'm still in trouble. The real situation is: the shares are open to everyone ( Everyone - full control ) The users ( new or old ) can't create files or directory on the shares. They can delete files and directory o write on files. The only way to allow the user to create new files is to put them in the Domain Admins Group or in another Group ( called EDP ). I tried to "clone" the EDP group ( same users rights ) but if I a put the users into this group they aren't able to create new files. I don't known there are some other group that enable the user to ceate files. up to now we've found only this two. I'm shure I'm missing something but I have a very little experience on PW on Digital Unix and I can't "see" the right way to fix this situation. About the mapuname error ( not mapuser as I wrote in .0 ) here are a couple of error messages. If someone is interested on the entire log I can post it. ------------------------------------------------------------------------------ ----------------------------------------------- 8# mapuname Unaligned access pid=1994 <mapuname> va=0x140012e4c pc=0x12005d0fc ra=0x12005d18 0 inst=0xb68b0000 Unaligned access pid=1994 <mapuname> va=0x140012e54 pc=0x12005d100 ra=0x12005d18 0 inst=0xb6ab0008 ------------------------------------------------------------------------------ ----------------------------------------------- Here are a couple of error messages from the samadm utility: ------------------------------------------------------------------------------ ----------------------------------------------- 8# samadm -C Unaligned access pid=1945 <samadm> va=0x14001364c pc=0x12005cf6c ra=0x12005cff0 inst=0xb68b0000 Unaligned access pid=1945 <samadm> va=0x140013654 pc=0x12005cf70 ra=0x12005cff0 inst=0xb6ab0008 ------------------------------------------------------------------------------ ----------------------------------------------- Any help will be very appreciated thanks Gabriele Casarotti [Posted by WWW Notes gateway] | |||||
| 1775.2 | Unaligned access is a performance issue | CPEEDY::VATNE | Peter Vatne, PATHWORKS for UNIX Server Engineering | Mon Mar 10 1997 11:58 | 33 |
>About the mapuname error ( not mapuser as I wrote in .0 ) here are a couple of >error messages. >If someone is interested on the entire log I can post it. >------------------------------------------------------------------------------ >----------------------------------------------- >8# mapuname >Unaligned access pid=1994 <mapuname> va=0x140012e4c pc=0x12005d0fc >ra=0x12005d18 >0 inst=0xb68b0000 >Unaligned access pid=1994 <mapuname> va=0x140012e54 pc=0x12005d100 >ra=0x12005d18 >0 inst=0xb6ab0008 >------------------------------------------------------------------------------ >----------------------------------------------- >Here are a couple of error messages from the samadm utility: >------------------------------------------------------------------------------ >----------------------------------------------- >8# samadm -C >Unaligned access pid=1945 <samadm> va=0x14001364c pc=0x12005cf6c >ra=0x12005cff0 >inst=0xb68b0000 >Unaligned access pid=1945 <samadm> va=0x140013654 pc=0x12005cf70 >ra=0x12005cff0 >inst=0xb6ab0008 >------------------------------------------------------------------------------ >----------------------------------------------- These are not strictly speaking errors, but warnings that certain data items are being accessed inefficiently. The programs should still operate correctly. If there are so many of these warnings that performance is unacceptable, then please report it officially. Otherwise, our plan is to eliminate these warnings in the next major release of PATHWORKS for UNIX. | |||||