SEO

Hi

First of all, excuse me because I am a very Newbie in the HP world from
France.

I own an old Apollo 715/50 under HPUX 9, that come from an university.

The first time I started this old stuff, I get vuelogin under X11.
Because of my lack of info (no login/password), I use PDC and ISL to change
root passwd

Now, when I boot (as root, because I only have this login for the moment), I
boot only in text mode !
My inittab specifie that vue start at level 3 or 4, and my init level is 4.

- I can't bring back my vuelogin,
- I don't know if it is possible to start X11 when already looged in console
mode.

Thanks for your help !

-------
Sébastien LE COCGUEN, un ingénieur à votre service
http://www.lecocguen.com
----------------------------------------------------------------------------
------------

I just want to add one thing :
If i manually start vuelogin ( "/usr/vue/bin/vuelogin" ), it write a new
line in Xerrors :
error (pid 1463) : Can not lock pid file /usr/vue/config/Xpid, another
Vuelogin is running (pid 221)

with "ps -e", i can see this process as 221.
So, the process is lauched, but that's all... :-(

> > - I can't bring back my vuelogin,
>
> Many problems with VUE (and CDE) are caused by networking problems.
> Make sure that your machine can resolve its hostname, etc. IIRC,
> there was a tool called dr_vue, that might be helpful.

I have change the SYSTEM_NAME. My be a cause, perhaps. I will change back to
the old name

> > - I don't know if it is possible to start X11 when already looged in
> > console mode.
>
> Why not? There should be script called x11start.

Great ! this script works. But no VUE, only X11.
Good begining, thanks

"Sébastien LE COCGUEN" <sebastien-nospam@lecocguen.com> writes:

>> I have change the SYSTEM_NAME. My be a cause, perhaps. I will
>> change back to the old name
>
> I have reseted to the old SYSTEM_NAME, but vue still doesn't start.
> the process is launched, but nothing at screen (and nothing in
> /usr/vue/bin/Xerrors !

I'm not sure if /etc/set_parms already existed on HP-UX 9.x; if it
did, you should use it to set the networking parameters. AFAIK,
nslookup must work. What does dr_vue say?

--
Michael Piotrowski, M.A. <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt>

> I'm not sure if /etc/set_parms already existed on HP-UX 9.x; if it
> did, you should use it to set the networking parameters.

I haven't this file

> nslookup must work. What does dr_vue say?

dr_vue says an interesting thing : "ERROR : I am unable to ping your
hostname."
I suppose this could be a cause of problem.

I have now to find what to do to correct that ! :-)
Thanks for your help.

Didn't catch the start of this thread. A few of my customers managed to
give machines the IP address 127.0.0.1 (the loopback addr). That will
cause CDE to bomb out. One also reported problems with 10.x.x.x which I
don't quite believe.

--
Who needs a life when you've got Unix? :-)
Email: john@unixnerd.demon.co.uk, John G.Burns B.Eng, Bonny Scotland
Web : http://www.unixnerd.demon.co.uk - The Ultimate BMW Homepage!
Need Sun or HP Unix kit? http://www.unixnerd.demon.co.uk/unix.html

"Sébastien LE COCGUEN" <sebastien-nospam@lecocguen.com> writes:

>> I'm not sure if /etc/set_parms already existed on HP-UX 9.x; if it
>> did, you should use it to set the networking parameters.
>
> I haven't this file

Hmm, then it was called something else. Anyway, you should be able to
use sam to set up networking. (Of course you could just edit the
configuration files, but using a tool avoids forgetting something.)

>> nslookup must work. What does dr_vue say?
>
> dr_vue says an interesting thing : "ERROR : I am unable to ping your
> hostname." I suppose this could be a cause of problem.

Well, what did I say? It's almost always a networking issue ;-)

> I have now to find what to do to correct that ! :-) Thanks for your
> help.

--
Michael Piotrowski, M.A. <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt>

Hi Sébastien

> dr_vue says an interesting thing : "ERROR : I am unable to ping your
> hostname."
> I suppose this could be a cause of problem.
Yes: Your nameresolution does not fit with your hostname and network
settings.

If you use the machine in a network the first step should be:

remove /etc/resolv.conf


/etc/hosts has to look like this:
------------------------------------
127.0.0.1 localhost loopback
xxx.xxx.xxx.xxx hostname hostname.
------------------------------------

xxx... is your IP adress. check it with netstat -in

hostname is the name you use in SYSTEM_NAME

watch the hostname_dot_ alias in the second line. It is required to keep
sendmail satisfied.




/etc/nsswitch.conf should look like this:
----------------------
hosts: files
networks: files
protocols: files
rpc: files
publickey: files
netgroup: files
automount: files
aliases: files
services: files
----------------------

Florian Anwander

> If you use the machine in a network the first step should be:
> remove /etc/resolv.conf
I haven't this file


> /etc/hosts has to look like this:
> ------------------------------------
> 127.0.0.1 localhost loopback
> xxx.xxx.xxx.xxx hostname hostname.
> ------------------------------------

It is

> /etc/nsswitch.conf should look like this:
I haven't this file

(HPUX 9)

NEWS :
Due to /etc/hosts modification, I have no errors in dr_vue, now.
But... it's still doesn't work.

Do you think it may be cause by the lack of the file "softspcd" (dr_vue
warning) ?
I haven't rm this file, and the installation was ok a week ago. I don't
think this file has disapeared since !