Noel:
What does your afsd_init.log say? You should see lines that read
similar to:
9:19:47 PM: Windows Loopback Adapter detected lana 13
9:19:50 PM: Netbios NCBADDNAME lana=13 code=0 retcode=0 complete=0
9:19:50 PM: Netbios NCBADDNAME added new name OMNIBOOK-AFS
9:19:50 PM: smb_Init
- Jeff
The hosts file on Windows is located at
%WINDIR%\SYSTEM32\DRIVERS\ETC\HOSTS
You could always run your own name server on one of your Linux systems
and configure Windows to rely on Linux for DNS.
Jeffrey Altman
Richard Eggert II wrote:
My single-server AFS cell is now playing nicely
Jason C. Wells wrote:
Today I can no longer get tokens. I get the error:
The AFS Client was unable to obtain tokens as jcw in cell
stradamotorsports.com.
Error: 11862791 (AFS service my not have started)
I cannot get tokens using MIT aklog either. I get the same error. I
appropriate given the scale of the problem today.
Jeffrey Altman
P.S. - The request number for this topic is 2628. I would appreciate it
if any new information you find would be submitted to the request. That
way when someone does find the time or resources to work on the cache
manager all
the cache is filled.
Jeffrey Altman
Rodney M Dyer wrote:
Jeffrey and others,
Today I've found a way to easily reproduce the bug in the AFS Windows
cache manager. It shows up rather easily as a leak in the handle
management. The number of handles rises out of control as files are
being copied
of OpenAFS you tested against. (Preferably something very recent due to
all of the memory
and handle allocation bugs which have been recently fixed.)
If there is a bug I would like to find it, if there is not I will
explain to you why the
behavior is what it is.
Jeffrey Altman
Rodney M Dyer wrote
Certainly if the code is merged into OpenAFS it will need to support
both MIT and Heimdal. I can't imagine that the work to do so would be
that great.
- Jeff
Ken Hornstein wrote:
Is there a reason the afs-krb5 migration kit is not merged into the
OpenAFS CVS?
I seem to recall from my
I assume that we could build these programs only an
--include-mit-krb5-support configuration option was specified.
- Jeff
Ken Hornstein wrote:
For aklog, it's probably not too bad. Some of the other tools are
distribution-specific, though.
Other than aklog and asetkey, what other
cell.
Jeffrey Altman
Theo van den Bout wrote:
Hi People
As far as i know:
* I cannot use the Windows AFS client because i need countless local XP
accounts
* I therefor have to use SAMBA as an AFS gateway
* I need windows roaming profiles
* and a NT domain
* with plain text
Rodney uses a modified version of the
integrated login which performs the kinit and aklog
steps in an external process instead of relying on the k4 support built
into OpenAFS.
More than likely he is bypassing the cause of the blue screen.
Jeffrey Altman
ted creedon wrote:
1. It's
I recommend you file a bug report with
Microsoft. AFS is not the only file system
that will suffer due to this behavior.
Jeffrey Altman
Derrick J Brashear wrote:
On Mon, 9 Feb 2004, Chris McClimans wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I still can't find
the community before I begin to
commit changes to the cvs-head. If you would be interested in participating
in this discussion please send a request to join the list at
[EMAIL PROTECTED]
Thank you.
Jeffrey Altman
___
OpenAFS-info mailing list
[EMAIL
Please use the web form
https://lists.openafs.org/mailman/listinfo/openafs-win32-devel
when subscribing to the [EMAIL PROTECTED] mailing list.
Thanks.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
When using Freelance mode you will not see cells until you
attempt to access them. This is not unexpected.
Please try to describe what you mean by the drive letters
tab going haywire in a form which will allow me to attempt
to reproduce it.
Jeffrey Altman
Tim C. wrote:
if you were experiencing
Jeffrey Altman wrote:
if you were experiencing problems with the 1.3.60 release, please
test the 20040319 build located at
http://web.mit.edu/~jaltman/Public/OpenAFS/
/afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/
I have once again refreshed the installers now dated 20040320.
These builds
to address these issues.
Are all of the systems on which people are reporting problem XP SP2?
Thanks
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
the following value to
the registry:
[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
"NoFindLanaByName" (DWORD) = 0x1
Jeffrey Altman
James Burns wrote:
I was also installing the server, so that is why it was greyed out
apparently. I am still, however, unable to configure the server because of
the error that I mentioned before, "Failed to determine current
configuration of this machine. Error: Unknown code d 43
Please try using the 1.3.62 client
which was announced last week.
http://www.openafs.org/release/openafs-1.3.62.html
If you do not subscribe to [EMAIL PROTECTED]. Please do so.
https://lists.openafs.org/mailman/listinfo/openafs-announce
Ulf Ziemann wrote:
-BEGIN PGP SIGNED
The 1.3.62 client allows you to adjust
the max MTU size and the use of Jumbograms.
Regkey:
[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
Value : RxNoJumbo
Type : DWORD {0,1}
Default : 0
Variable: rx_nojumbo
If enabled, does not send or indicate that we are able to
The registry settings are documented in
the CVS at doc/txt/winnotes/registry.txt
I am not familiar enough with the Linux client to be able to answer the
question.
Ulf Ziemann wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
is there a similar solution for linux
Jason C. Wells wrote:
Will the "Convert to IFS" statement result in being able to use proper
global root convention, namely /afs?
If so, Yay!
THanks,
Jason
I doubt we will ever get /afs unless it is /afs
off of some drive letter.
The closest we can get would be a UNC name of
Rodney M Dyer wrote:
At 11:22 AM 5/11/2004,
Jeffrey Altman wrote:
I added the
support to Windows. Doug did most of the
work on the Unix side.
I haven't checked this, as we have not removed KAS from our equation,
but does the new klog obtain Krb 5 tickets and stuff
David Miller wrote:
I've also had a bit of a look into a GUI for openafs.
the Java API looked promising, but requires a kaserver cell.
so doesnt work with kerberos setups
Java supports Kerberos 5 (DES only) built-in. It can obtain
Kerberos credentials from the OS cache
.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
, this will cause problems
if you are frequently
disconnected from the network.
Jeffrey Altman
Gabe ListAccount wrote:
Hello,
I'm Running AFS clientversion 1.3.6390 on a windows XP Pro
machine. I have a client on several other XP and linux machines and
have no problems. However, The service appears
principal for the AFS cell. Then
there is a cross-realm
trust between Active Directory and the MIT realm. Therefore, I can
force the
service tickets to be DES-CBC-CRC and be of small enough size to be
used directly
with the 1.2.11 AFS servers while still using pure Kerberos 5.
Jeffrey Altman
Vaclav Janoch wrote:
I'm running the latest versions which are currently available.
Server: Version 1.2.11 (for RedHat 9.0)
Client: OpenAFSforWindows-1-3-6400.exe
How are you obtaining the tokens for your cell?
smime.p7s
Description: S/MIME Cryptographic Signature
Which version of the OpenAFS client are you using?
What are the contents of %WINDIR%\TEMP\afsd.log and
%WINDIR%\TEMP\afsd_init.log after the panic?
Jeffrey Altman
Mason . wrote:
Hi everyone,
I'm desperately trying to get OpenAFS working on my XP machine but I'm
running into the following
This would clearly be the result of a very bad coding error.
What version of the client is on the machines which is producing this
request?
Is it a Kerberos 5 or Kerberos 4 request?
Jeffrey Altman
David Botsch wrote:
Fascinating.
We have also noted, since upgrading to kerb5 (yes, it worked
: smb_localNamep is MASON-AFS
6/10/2004 10:12:50 AM: lana_list.length 0
You have no valid network adapters to bind to. Install the Microsoft
Loopback Adapter.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
David Botsch wrote:
I should add we've been unable to manually make this happen (and do
not know for sure it is afs causing it).
1.2.8a on the clients and the servers are 1.3.3 (straight from the MIT
source).
It is a version 4 request.
It could be a bug in the AFS Kerberos 4 authentication
Mitch Collinsworth wrote:
I've been wondering if it might be somehow related to the windows
authentication behavior described in this paper:
http://www.usenix.org/publications/library/proceedings/lisa2000/beck.html
-Mitch
Not if it is a Kerberos 4 request. Microsoft Windows does not use
and prototypes.
You want to use krb524d with the keytab option.
Jeffrey Altman
Copyright 1994 by OpenVision Technologies, Inc.
Permission to use, copy, modify, distribute, and sell this software
and its documentation for any purpose is hereby granted without fee,
provided that the above
Why are you attempting to use 1.3.5299?
the current release is 1.3.6400
Jeffrey Altman
William Isaac Winston wrote:
Hello,
I tried to upgrade to openafs verson 1.3.5299. However, I have
run into serveral problems. The main problem is I can not change the
Volume Location Server
Christopher D. Clausen wrote:
On Tuesday, June 15, 2004 12:35p [EMAIL PROTECTED] wrote:
Christopher D. Clausen wrote:
Would it be possible to have a registry key that determines if normal
users can run the fs commands? I personally do not care if a user
wants encryption or not if it is a single
I recommend you add support either for RC4-HMAC keys to your principals.
RC4-HMAC keys will be the first enctype in the list from Windows clients.
The second enctype in the list will be DES-CBC-MD5; followed by DES-CBC-CRC.
Jeffrey Altman
David Botsch wrote:
So, we've migrated our kaserver
[EMAIL PROTECTED] wrote:
--On Friday, June 18, 2004 12:04 AM -0400 Jeffrey Altman
[EMAIL PROTECTED] wrote:
There was a race condition associated with the establishment of global
drives which was fixed
post-1.3.64. Please try one of the daily builds and see if it indeeds
solves your problem
[Please keep mailing list discussions on the mailing list]
Lukas Kubin wrote:
Jeffrey Altman wrote:
Lukas Kubin wrote:
I'm using MIT Kerberos for Windows 2.6.0 and OpenAFS 1.3.6500 on
Windows XP. My computer is member of NT-style domain driven by Samba
server.
The current release of KFW
at the text. I am
sure the community will provide ample review when the time comes.
Are there any volunteers?
Thanks.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
Use DNS to distribute server information instead of the CellServDB file
then you can
keep it up to date for all of your machines from one location.
CellServDB entries supercede DNS ones. So if you have an out of date
CellServDB file
you won't find the servers.
Robbie Foust wrote:
Hi,
Sorry if
with experience in OpenAFS and Kerberos to review the pages and
use the
Edit feature of the Wiki to correct, enhance, or clarify the information
which is
presented there.
Thanks
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
have done is specified a
directory within which the mount
point should be created.
In the above table csc-cowboy, afs2-cowboy, and all are submount
(share) names not mount points.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
Please read afs-install-notes.txt and registry.txt
Jeffrey Altman
Miles Davis wrote:
On Fri, Jul 23, 2004 at 01:48:32PM -0400, Jeffrey Altman wrote:
Wake is a replacement for Leash32 (from MIT Kerberos for Windows)
and afscreds.exe (from OpenAFS) which was needed when neither
Not starting afscreds automatically was not what you were looking for.
Not auto initializing tokens is what you are looking for
Miles Davis wrote:
On Thu, Jul 29, 2004 at 01:59:18PM -0400, Jeffrey Altman wrote:
Please read afs-install-notes.txt and registry.txt
Hrmm
Integrated Login means integrated with the Windows Login.
First, demonstrate you can obtain tokens using Leash or Afscreds.
What you do next is dependent upon how your user authenticates to the
Windows machine
and how the machine is configured with regards to the Kerberos realm
which
for Windows 1.3.70 will ship without installing this key.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
PROTECTED] to different
users when both the FOO.COM and BAR.COM realms are trusted by the
foobar.com cell.
If there is a mapping to be applied it should be applied within the
authorization database (ptserver) not in something that modifies
authentication names.
Jeffrey Altman
smime.p7s
Description: S
the authorization database needs to make a
decision on what access to grant.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
problem is that the token being generated is too
large for the server to handle. Apply Doug's patches to 1.2.11 or
help us prepare for 1.4 by using 1.3.70.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
The problems I have discussed are only on Windows. There will
be a new build soon. Daily builds are available for those who
want to help test.
OpenAFS for Windows does not contain large file support.
Jeffrey Altman
David Thompson wrote:
Jeffrey Altman wrote:
Now the remaining problem
Client Side
Caching to decide to serve things locally.
Jeffrey Altman
[EMAIL PROTECTED] wrote:
Has anyone ever tried to use the Windows Offline folders or Briefcase
utilities with AFS and XP ?
I'm playing around with it, but it doesn't seem overly stable. I'd
like to hear others views, opinions
If Windows has decided that you are offline and
is redirecting all traffic to the offline copy
you will be hosed. GetToken operations require
the ability to communicate to the AFS Server via
the creation of files via SMB/CIFS. If you are
offline, you can't do that.
Jeffrey Altman
[EMAIL
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
2b token
aklog -4 = use a Kerberos 4 TGT to obtain a Kerberos 4 afs service
ticket and repackage the Kerberos 4 ticket as an afs token
You do not need to upgrade all of your clients when you upgrade your
servers. You should upgrade your servers first and then your clients.
Jeffrey Altman
Remove the second version of KFW which is installed on your machine
and which is earlier in your PATH.
Robbie Foust wrote:
Ok, the aklog -4 seems to have done the trick. Thanks for the help!
I do have another question though. The aklog that comes with KFW 2.6.4
works, but if I use the one that
tickets.
Jeffrey Altman
Finke, Jon wrote:
Hey Folks,
Sorry to hit the general mailing list, but I have been hitting a problem
that has been seen before, but the bug tracker wont let me see the
resolution.
I am running Windows XP Pro (no SP2 yet), with AFS V1.3.7100, and my AFS
client seems
-dump will log some information which might be useful as
part of a real-time debugging effort. Otherwise, connecting a debugger
to AFS Client Service might be necessary if it is indeed an AFS Client
problem.
What does the SysInternals filemon.exe tool report?
Jeffrey Altman
smime.p7s
it for
something else; then read the registry.txt file and set the
appropriate registry value to disable KFW support. The registry.txt
file is located on the same page you downloaded the installer from.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
Lee Damon wrote:
If, on the other hand, you are only documenting the windows port of AFS, then
word might make sense.
If you are working on documenting the Windows port, please do so in
conjuction with Tommie Gannert.
Thanks.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
I think Allen Moy is trying to explain to you what might be wrong
with your servers as visible from your Windows client. Is your
new server multihomed?
Jeffrey Altman
Ron Croonenberg wrote:
Apparently there's someone who experienced similar problems with windows clients
and a second afs server
not heavily used in the past on your machines.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
session. Therefore KFW will never have
tickets. If you want the users to obtain K5 tickets and have them
be used in the logon session, the workstation must obtain them via
Microsoft's Kerberos LSA.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
/src/WINNT/client_config/drivemap.cpp
Ron Croonenberg wrote:
Hi Jeff,
where in the client source is the drive mapping done ?
thanks,
Ron
smime.p7s
Description: S/MIME Cryptographic Signature
properly in the MSI. If they are not configured
properly it would be a bug that should be filed at [EMAIL PROTECTED]
Jeffrey Altman
Lukas Kubin wrote:
Thank you for your answer.
I found a problem with creating the registry values of .msi installer
using Orca: I set the registry values correctly
Rodney M Dyer wrote:
At 09:40 AM 10/13/04, Jeffrey Altman wrote:
Integrated login cannot pass Kerberos 5 tickets from the Network
Provider to the users logon session. Therefore KFW will never have
tickets. If you want the users to obtain K5 tickets and have them be
used in the logon session
Lukas Kubin wrote:
May I have one more question? Is there any option how to tell OpenAFS
not to show the AFS login window after logging in using local account only?
the startup options for the AFS Systray tool (afscreds.exe) are stored
in AfscredsShortcutParams. Removing the -A' parameter will
Jeffrey Altman wrote:
This bug should be fixed in the current daily builds.
//afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS
I would appreciate it if you would ask your user to test it.
The following was posted when the 1.3.7 client came out. Is the official
word that the windows OpenAFS
consider this problem serious enough that we are going to release
1.3.72 over the weekend in order to get the client side patches
out there for Windows users. On Monday you will be testing the
released build.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
.
Jeffrey Altman
Alan Wehmann wrote:
The problem turned out to be non-existant IBM\AFS\etc. directories
in the PATH environmental variable on my laptop. When I removed them
and restarted the computer, the OpenAFS 1.3.71 client worked.
I don't know how those PATH entries got there. Perhaps
not
support Kerberos 5 tickets as tokens.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
There is no IBM path information in the 1.3.xx installers for
OpenAFS. We completely replaced the installer from scratch.
Did you install the older 1.2.xx version of OpenAFS on your machine?
If so, that is most likely where it came from.
Jeffrey Altman
Alan Wehmann wrote:
This is a personal
-rw
or something like that.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
What makes you think that the libafsconf.dll file cannot be found?
Jeffrey Altman
Lars Schimmer wrote:
Hi!
We have a problem with the Windows OpenAFS Client 1.3.7100 under Windows
XP SP2.
The user installed some version 1.2.6x and wanted to upgrade.
After the upgrade the OpenAFS couldn't find
\OpenAFS\Client\Program directory.
Jeffrey Altman
Lars Schimmer wrote:
Jeffrey Altman wrote:
| What makes you think that the libafsconf.dll file cannot be found?
There's a requester that shows this message :-)
Installed with loopback device, use integrated logon, login error: wrong
password (yes
it cannot start?
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
.
It should not die with a page fault. Feel free to open a ticket
on this issue by sending mail to [EMAIL PROTECTED] describing
your problem. One problem per e-mail. Each e-mail will open a new
ticket in the Request Tracker.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
Sounds like SMB shares are being virus scanned
Joe Buehler wrote:
We recently upgraded to version 9 of Symantec's AntiVirus
and now some (not all!) users are unable to use the Cygwin X server
via the Windows AFS client.
On the 2 machines I have looked at, the afsd_service.exe process
and System
the need for Global Drives no
longer exists and they should not be used.
Jeffrey Altman
Ron Croonenberg wrote:
Hello all,
I am still having issues with mapping drives with the windows xp client.
However I found a way around it
When I use the AFS client and try to map a drive via the drive letters
internals sitting down on a
machine that suffers from the problem with a debugger to identify what
requests are being received from the Windows SMB/CIFS client and why
those requests are not being processed successfully. At the moment I
don't have time to volunteer to do this.
Jeffrey Altman
it is is subtle. The only way to track this down is with
access to an affected machine, a debugger, and time.
Jeffrey Altman
=
1879:
Thomas Edison gets an idea, and his brother Timmy says,
Hey, what's that thing over your
too have used clean XP SP2 installs without problems. There must be
something different about your environment which makes a difference.
Whatever it is is subtle. The only way to track this down is with
access to an affected machine, a debugger, and time.
Jeffrey Altman
smime.p7s
Ron Croonenberg wrote:
Hi Jeff,
I can check, but I doubt it.
thanks
btw: I installed the DEBUG version of the client on that one machine. Where are
the log/debug files so I can take a look at what is going on ?
debug does not mean additional logs. what it means is that it was
compiled without
the afs drivemap library pretty much passes requests onto the WNet APIs
for performing drive mapping. What I would accept as a statement is
that the Explorer Shell uses the APIs differently from how the AFS drive
mapping API does it.
I would be interested in knowing if you are able to
When you mapped the drive using afscreds.exe you specified a submount
name.
Are you able to access the submount when you map via NET USE or the
Explorer Shell?
NET USE X: \\AFS\submount
smime.p7s
Description: S/MIME Cryptographic Signature
to go.
The consistent path is the UNC path as described above.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
configuration data.
Jeffrey Altman
Charles McIntyre wrote:
In the innocent world before SP2, we used OpenAFS 1.2.10 on all our lab
PCs. When a user logged in, a script would run, awk the campus passwd
file, find their home directory and write out a new afsdsbmt.ini file.
When the user wanted
as well as in kind assistance are seriously appreciated.
Tax deductible donations may be made via the OpenAFS account within
Usenix (a 501c3 corporation.)
Jeffrey Altman
OpenAFS for Windows Gatekeeper
smime.p7s
Description: S/MIME Cryptographic Signature
The difference between 1.3.72 and 1.3.73 is simply a mistake in the
source tree. However, to avoid confusion I am building 1.3.73 branded
binaries. They will be posted shortly.
Jeffrey Altman
Matthew Cocker wrote:
In
http://www.openafs.org/dl/openafs/1.3.73/winnt/
there are files abled
domains this might be impossible to so which is one reason
why this architecture along with any architectures which perform
principal name re-writing are to be avoided.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
. This
might or might not provide some clues.
The output of SysInternal's filemon.exe would also provide some insight
into what it is that MatLab is trying to do.
Jeffrey Altman
John W. Sopko Jr. wrote:
The user that was having the problem upgraded to OpenAFS 1.3.73 and is
still
having problems. He goes
path.
Jeffrey Altman
David Bear wrote:
I'm starting to use the afsshare program thats part of the openafs
1.3.x distribution for windows. I assume the submount entries would be
stored in the current user portion of the registry -- but it looks
like they are stored under local-machine/software
a fixed size was thrashing. I should
probably consider increasing the default in the next release to a higher
number.
Jeffrey Altman
Jeffrey Altman wrote:
Ok. So the client has an additional bug. At least the windows 1.3.73
client is no longer crashing your file server. ;)
the best would
not to be what I was looking for.
The Windows client uses unsigned long for all volume IDs. The Unix
client should probably switch to using afs_uint32.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
in the local file system they are creating
afsws - anl.gov/@sys/usr/afsws
in the root.afs volume. Maybe the answer is to add symlink support to
dynamic roots but I think we want to document that this kind of setup
should be avoided. Or am I completely nuts?
Jeffrey Altman
smime.p7s
Description: S
. These will be maintained
in the registry to survive service session restart.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
, then you will not see any data. You can
manually modify the mount point to refer to root.afs using the fs
mkmount and fs rmmount commands.
If you are not using Freelance, then Windows will mount the root.afs
volume of the default cell.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic
Lars Schimmer wrote:
Derrick J Brashear schrieb:
Right now OpenAFS 1.3.73 on WindowsXP sp2 runs fine, much better than
1.3.71 or
1.3.72, which crashed 6 times a day.
Did you file a bug report about these crashes?
Jeffrey Altman
___
OpenAFS-info mailing
, especially if they are
regularly reproducible I want to see the stack traces. This is why
we ship installers which contain debugging symbols.
If users of the software do not report the problems they encounter,
how am I supposed to fix them?
Jeffrey Altman
. In the OpenAFS Request Tracker
there is an open ticket for this:
15523: Windows Power Management fails to do the correct thing
http://rt.central.org/rt/Ticket/Display.html?id=15523
Jeffrey Altman
James Burns wrote:
Jeffrey,
Do you have a check list of the steps a person should go through
1 - 100 of 2474 matches
Mail list logo
