[OpenAFS-devel] fs sysname assignment problem

Tue, 21 Jun 2005 12:58:59 -0400

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C57682.84E25A60
Content-Type: text/plain

You have to give the -newsys option more than once:

# fs sysname -newsys i386_linux26 -newsys i386_blah
fs: new sysname list set.
# fs sysname
Current sysname list is 'i386_linux26' 'i386_blah'
#

James

-----Original Message-----
From: Christof Hanke [mailto:hanke@rzg.mpg.de] 
Sent: Tuesday, June 21, 2005 11:52 AM
To: John A. Goebel; openafs-devel@openafs.org
Subject: Re: [OpenAFS-devel] fs sysname assignment problem

John A. Goebel wrote:

>Ok, so then I don't understand sysname. I thought I could simply give
>a list of values to @sys via the 'fs sysname'. Example:
>
>root@frankendog:~# /usr/afsws/bin/fs sysname
>Current sysname list is 'i386_linux26' 'i386_rhel30'
>root@frankendog:~# /usr/afsws/bin/fs sysname -newsys foo
>fs: new sysname set.
>root@frankendog:~# /usr/afsws/bin/fs sysname
>Current sysname is 'foo'
>root@frankendog:~# /usr/afsws/bin/fs sysname -newsys foo bar
>fs: new sysname list set.
>root@frankendog:~# /usr/afsws/bin/fs sysname
>Current sysname list is 'foo' 'bar'
>
>My other systems can have multiple values for @sys assinged in this manner,
as
>you can see. Have something changed in 1.3.84 (I don't see anything in this
>regard in the changelog) or am I not understand your answer?
>  
>
Well, you should ask somebody with more experience with afs than me.
I can't set more than one name :
"""
senf:~ # fs sysname
Current sysname is 'i386_su92'
senf:~ # fs sysname i386_su92 i386_linux26
fs: Too many values after switch -newsys
"""
This is on a pre-1.3.84

"""
senf:~ # rxdebug localhost 7001 -v
Trying 127.0.0.1 (port 7001):
AFS version:  OpenAFS 1.3.79 built  2005-03-03
"""

It's on linux, maybe you're using some other OS.
Sorry but I haven't seen that before, neither on linux nor on solaris.

-Christof

_______________________________________________
OpenAFS-devel mailing list
OpenAFS-devel@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-devel

Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

------_=_NextPart_001_01C57682.84E25A60
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=
=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version=
 5.5.2653.12">
<TITLE>RE: [OpenAFS-devel] fs sysname assignment problem</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>You have to give the -newsys option more than=
 once:</FONT>
</P>

<P><FONT SIZE=3D2># fs sysname -newsys i386_linux26 -newsys=
 i386_blah</FONT>
<BR><FONT SIZE=3D2>fs: new sysname list set.</FONT>
<BR><FONT SIZE=3D2># fs sysname</FONT>
<BR><FONT SIZE=3D2>Current sysname list is 'i386_linux26'=
 'i386_blah'</FONT>
<BR><FONT SIZE=3D2>#</FONT>
</P>

<P><FONT SIZE=3D2>James</FONT>
</P>
<BR>

-----Original Message-----
 From: Christof Hanke [<A HREF=
=3D"mailto:hanke@rzg.mpg.de">mailto:hanke@rzg.mpg.de</A>] 
 Sent: Tuesday, June 21, 2005 11:52 AM
 To: John A. Goebel; openafs-devel@openafs.org
 Subject: Re: [OpenAFS-devel] fs sysname assignment=
 problem

<P><FONT SIZE=3D2>John A. Goebel wrote:</FONT>
</P>

&gt;Ok, so then I don't understand sysname. I thought I=
 could simply give
 &gt;a list of values to @sys via the 'fs sysname'.=
 Example:
 &gt;
 &gt;root@frankendog:~# /usr/afsws/bin/fs sysname
 &gt;Current sysname list is 'i386_linux26'=
 'i386_rhel30'
 &gt;root@frankendog:~# /usr/afsws/bin/fs sysname -newsys=
 foo
 &gt;fs: new sysname set.
 &gt;root@frankendog:~# /usr/afsws/bin/fs sysname
 &gt;Current sysname is 'foo'
 &gt;root@frankendog:~# /usr/afsws/bin/fs sysname -newsys=
 foo bar
 &gt;fs: new sysname list set.
 &gt;root@frankendog:~# /usr/afsws/bin/fs sysname
 &gt;Current sysname list is 'foo' 'bar'
 &gt;
 &gt;My other systems can have multiple values for @sys=
 assinged in this manner, as
 &gt;you can see. Have something changed in 1.3.84 (I=
 don't see anything in this
 &gt;regard in the changelog) or am I not understand your=
 answer?
 &gt;&nbsp; 
 &gt;
 Well, you should ask somebody with more experience with=
 afs than me.
 I can't set more than one name :
 &quot;&quot;&quot;
 senf:~ # fs sysname
 Current sysname is 'i386_su92'
 senf:~ # fs sysname i386_su92 i386_linux26
 fs: Too many values after switch -newsys
 &quot;&quot;&quot;
 This is on a pre-1.3.84

<P><FONT SIZE=3D2>&quot;&quot;&quot;</FONT>
<BR><FONT SIZE=3D2>senf:~ # rxdebug localhost 7001 -v</FONT>
<BR><FONT SIZE=3D2>Trying 127.0.0.1 (port 7001):</FONT>
<BR><FONT SIZE=3D2>AFS version:&nbsp; OpenAFS 1.3.79 built&nbsp;=
 2005-03-03</FONT>
<BR><FONT SIZE=3D2>&quot;&quot;&quot;</FONT>
</P>

<P><FONT SIZE=3D2>It's on linux, maybe you're using some other OS.</FONT>
<BR><FONT SIZE=3D2>Sorry but I haven't seen that before, neither on linux=
 nor on solaris.</FONT>
</P>

<P><FONT SIZE=3D2>-Christof</FONT>
</P>

<P><FONT SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>OpenAFS-devel mailing list</FONT>
<BR><FONT SIZE=3D2>OpenAFS-devel@openafs.org</FONT>
<BR><FONT SIZE=3D2><A HREF=
=3D"https://lists.openafs.org/mailman/listinfo/openafs-devel" TARGET=
=3D"_blank">https://lists.openafs.org/mailman/listinfo/openafs-devel</A></F=
ONT>
</P>

</BODY>
</HTML>
<table><tr><td bgcolor=3D#ffffff><font color=3D#000000>Notice: The=
 information contained in this e-mail message and/or attachments to it may=
 contain confidential or privileged information. If you are not the=
 intended recipient, any dissemination, use, review, distribution, printing=
 or copying of the information contained in this e-mail message and/or=
 attachments to it are strictly prohibited. If you have received this=
 communication in error, please notify us by reply e-mail or telephone and=
 immediately and permanently delete the message and any attachments. Thank=
 you<br>
<br>
</font></td></tr></table>
------_=_NextPart_001_01C57682.84E25A60--