From: "Caerwyn Jones" <caerwynj@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Acme-SAC fstat issue?
Date: Fri, 23 Nov 2007 11:55:03 -0500 [thread overview]
Message-ID: <ff4df6da0711230855y1ee82beak5bd6a4d1a2341b21@mail.gmail.com> (raw)
In-Reply-To: <1c88e077e0ec2c4353419feb147e821d@terzarima.net>
Here's another go at working around these issues when a SID can't be
mapped to a name.
In the sidtouser() function if the name isn't mapped I return an
"unknown" for that sid.
--- /n/D/inferno-os/emu/Nt/devfs.c Wed Nov 21 22:53:06 EST 2007
+++ /sys/emu/Nt/devfs.c Fri Nov 23 11:51:39 EST 2007
@@ -1867,8 +1867,10 @@
gsid = osid;
owner = sidtouser(srv, osid);
+ if(owner == 0)
+ return 0;
group = sidtouser(srv, gsid);
- if(owner == 0 || group == 0)
+ if(group == 0)
return 0;
/* no acl means full access */
@@ -2063,9 +2065,8 @@
naname = sizeof(aname);
ndname = sizeof(dname);
-
if(!LookupAccountSidW(srv, s, aname, &naname, dname, &ndname, &type))
- return nil;
+ return mkuser(s, SidTypeUnknown, L"unknown", L"unknown") ;
return mkuser(s, type, aname, dname);
}
On Nov 7, 2007 4:20 AM, Charles Forsyth <forsyth@terzarima.net> wrote:
> >What does it mean when acme-SAC says:
>
> >can't fstat /n/c/dev/Users/plalonde/readme: The trust relationship
> >between this workstation and the primary domain failed?
>
> it sounds as though it's heading for therapy.
> it's just repeating a diagnostic from Windows.
> i've seen peculiar effects when a workstation was disconnected
> from the machine declared to be the domain controller and seemed to work until the
> cached security records timed out.
>
prev parent reply other threads:[~2007-11-23 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 5:14 Paul Lalonde
2007-11-07 9:20 ` Charles Forsyth
2007-11-23 16:55 ` Caerwyn Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff4df6da0711230855y1ee82beak5bd6a4d1a2341b21@mail.gmail.com \
--to=caerwynj@gmail.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).