« Wayback Wed: Charon's coming out, at a pub | Main | Second generation of migration begins »

May 18, 2018

Fine-Tune: Setting up a 3000 as file server

I would like to set up an HP 3000 as a file server. In one of my accounts I want to have a share for my 100 users pointing to a separate directory in this account. The homes section in smb.conf normally points to the home group of the user, which is the same for all of them and is not helpful. Is there another way of solving the problem, or must I configure more than the 100 shares?

Mark Wonsil replies:

I saw a clever little trick in Unix that should work on MPE:

[%U]
path = /ACCT/SHARES/%U

This creates a share name that is the same as the username and then it points the files to a directory under the SHARES group.

How do I set my prompt setting in the startup script?

John Burke replies:

Here’s what I do for my prompt:
SETVAR HPPROMPT,”<SASHA: “+&
“!!HPJOBNAME,!!HPUSER.!!HPACCOUNT,!!HPGROUP> “+&
“!!HPDATEF !!HPTIMEF <!!HPCWD>”+CHR(13)+CHR(10)+”[!!HPCMDNUM]:”

This yields, for example,
<SASHA: JPB,MGR.SYSADMIN,PUB> THU, FEB 20, 2003 11:15 PM </SYSADMIN/PUB>
[7]:

A disk drive has failed on a user volume. How can I determine the accounts and groups on that user volume?

John Clogg replies:

Try REPORT @.@;ONVS=<volset>

Jeff Woods adds:

In addition to the suggestion to use “:REPORT @.@;ONVS=volset” (which may fail because it’s actually trying to look at the group entries on the volume set) you can do a “:LISTGROUP @.@” and scan the listing for groups where HOMEVS is your uservolumesetname. The advantage of LISTGROUP is that it uses only the directory entries on the system volume set. You may want to redirect the output of LISTGROUP to a file and then search that rather than trying to scan the listing directly.

04:43 PM in Hidden Value | Permalink

Bookmark and Share

Use our search engine to find 20 years
of HP 3000 news and articles

Comments

Comments

The comments to this entry are closed.