I run a couple of parallel systems, sharing the same home directory.

I have a SuSE linux \ and a Slackware \.

I'm noticing a difference in behavior when initiating a ppp
dialup connection.

I have an options file with debug in it, so I can watch
the ppp connection.

/dev/ttyS3
115200
crtscts
lock
user me
noipdefault
defaultroute
debug

I call the dialup with the standard script:

#!/bin/sh
#ppp-on
/usr/sbin/pppd connect '/usr/sbin/chat -v -f /etc/ppp/z.chat' \
file '/etc/ppp/z.options'

So under SuSE, it works like I want, the debug information is printed to
the screen, and I can easily kill the connection with Cntrl-C.

Under Slackware, it just starts it and puts it into the background, as
if I ran it with an &. And the slackware shell will just print my local
and remote IP address when the connection is up, but the debug
information is missing. Plus the Slackware bash shell will continue to
take commands, where the SuSE shell only responds to control-c.

So what is happening and what do I need to do to the Slackware setup
to make it show the debugging information, and respond to control-c?




--
I'm not really a human, but I play one on earth.
http://zentara.net/japh.html

zentara <zentara@highstream.net> wrote:
> /usr/sbin/pppd connect '/usr/sbin/chat -v -f /etc/ppp/z.chat' \
> file '/etc/ppp/z.options'

If all files are the same, then there should be no difference in
execution. So, you have different setups.

--
William Park, Open Geometry Consulting, <opengeometry@yahoo.ca>
Linux solution/training/migration, Thin-client

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, zentara dared to utter,
> I have a SuSE linux \ and a Slackware \.

Did anyone else read this as:

I have a SuSE linux and a Slackware .

That should be /. See how Windows has corrupted our kind!

> I'm noticing a difference in behavior when initiating a ppp
> dialup connection.
>
> I call the dialup with the standard script:
>
> #!/bin/sh
> #ppp-on
> /usr/sbin/pppd connect '/usr/sbin/chat -v -f /etc/ppp/z.chat' \
> file '/etc/ppp/z.options'
>
> So under SuSE, it works like I want, the debug information is printed to
> the screen, and I can easily kill the connection with Cntrl-C.
>
> Under Slackware, it just starts it and puts it into the background, as
> if I ran it with an &. And the slackware shell will just print my local
> and remote IP address when the connection is up, but the debug
> information is missing. Plus the Slackware bash shell will continue to
> take commands, where the SuSE shell only responds to control-c.
>
> So what is happening and what do I need to do to the Slackware setup
> to make it show the debugging information, and respond to control-c?

This sounds like Slackware's default dial-up behavior. When you run
ppp-setup (something like that I think) to setup a dial-up internet
connection, it makes some config file changes, then lets you run a
script to go online. It dials-up, establishes a connection, and drops
into the background. IIRC it prints your IP address out on a successful
connection, but I could be wrong.

So where am I going with this? Well, I'd reccomend you make a back-up
of the /etc/ppp directory on your Slackware machine. A tar gzip should
do nicely.

# tar -cvzf /root/ppp.tar.gz /etc/ppp

Now copy the SuSE /etc/ppp directory into place on the Slackware /.

# cp -aR /path/to/SuSE/root/etc/ppp /etc/ppp

Now give it a try and see what it does. If it behaves the way you
expect, compare the differences in the two /etc/ppp directories.

> --

You're news reader is broke. That .sig delimeter should be "-- " (note
the space). Your's is simply "--".

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAc33oL3KiNGOqr6ERAoX7AJ9RBFuxFiXv7LwstULXnh cg2Hhk6ACg1eWF
HuZ5nfUoIY1Uh0UwyNZIIAY=
=AZIe
-----END PGP SIGNATURE-----

On 6 Apr 2004 23:05:00 -0500, Alan Hicks <alan@lizella.netWORK> wrote:


>This sounds like Slackware's default dial-up behavior. When you run
>ppp-setup (something like that I think) to setup a dial-up internet
>connection, it makes some config file changes, then lets you run a
>script to go online. It dials-up, establishes a connection, and drops
>into the background. IIRC it prints your IP address out on a successful
>connection, but I could be wrong.

Yes, that is the default behavior, but what if you want debug output?


>> --
>
>You're news reader is broke. That .sig delimeter should be "-- " (note
>the space). Your's is simply "--".

Thanks for pointing that out.



--
I'm not really a human, but I play one on earth.
http://zentara.net/japh.html

zentara <zentara@highstream.net> wrote:
>On 6 Apr 2004 23:05:00 -0500, Alan Hicks <alan@lizella.netWORK> wrote:
>
>>This sounds like Slackware's default dial-up behavior. When you run
>>ppp-setup (something like that I think) to setup a dial-up internet
>>connection, it makes some config file changes, then lets you run a
>>script to go online. It dials-up, establishes a connection, and drops
>>into the background. IIRC it prints your IP address out on a successful
>>connection, but I could be wrong.
>
>Yes, that is the default behavior, but what if you want debug output?

(Warning: Reading man pages is manditory!)

Both pppd and chat are producing messages.

See the debug section of the pppd man page. See also the man
pages for syslogd and syslog.conf to determine both what your
system is doing now, and what you might like it to do. Chat has
a variety of options which modify its behavior. See the man
page, and look at the -r, -e, -v, -V, -s, and -S options.

It is fairly likely that the differences you are seeing have to
do which options are used for chat when it is invoked by pppd.
Look at your configuration files in /etc/ppp.

I personally *much* prefer that all of the messages be sent to
syslogd. If I want to actually watch them in real time, I just
crank up another xterm window running bash, su to root, and do
"tail -f /var/log/messages", for example. But I only want to
see that once in a rare while, and the rest of the time it just
saves everything for me, just in case I need to see it later.

--
Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd@barrow.com

zentara wrote:

> I run a couple of parallel systems, sharing the same home directory.
>
> I have a SuSE linux \ and a Slackware \.
>
> I'm noticing a difference in behavior when initiating a ppp
> dialup connection.
>
> I have an options file with debug in it, so I can watch
> the ppp connection.
>
> /dev/ttyS3
> 115200
> crtscts
> lock
> user me
> noipdefault
> defaultroute
> debug
>
> I call the dialup with the standard script:
>
> #!/bin/sh
> #ppp-on
> /usr/sbin/pppd connect '/usr/sbin/chat -v -f /etc/ppp/z.chat' \
> file '/etc/ppp/z.options'
>
> So under SuSE, it works like I want, the debug information is printed to
> the screen, and I can easily kill the connection with Cntrl-C.
>
> Under Slackware, it just starts it and puts it into the background, as
> if I ran it with an &. And the slackware shell will just print my local
> and remote IP address when the connection is up, but the debug
> information is missing. Plus the Slackware bash shell will continue to
> take commands, where the SuSE shell only responds to control-c.
>
> So what is happening and what do I need to do to the Slackware setup
> to make it show the debugging information, and respond to control-c?
>
>
>
>
> --
> I'm not really a human, but I play one on earth.
> http://zentara.net/japh.html

And we care because.... ?

--
"The sooner all the animals are dead, the sooner we'll find their
money."
-- Ed Bluestone, "The National Lampoon"

NeoSadist <neosad1st@charter.net> says...

>And we care because.... ?

We care because we like helping people who have Slacware questions.

--
Guy Macon, Electronics Engineer & Project Manager for hire.
Remember Doc Brown from the _Back to the Future_ movies? Do you
have an "impossible" engineering project that only someone like
Doc Brown can solve? My resume is at http://www.guymacon.com/

On Wed, 07 Apr 2004 13:39:26 -0700, Guy Macon <http://www.guymacon.com>
wrote:

>
>NeoSadist <neosad1st@charter.net> says...
>
>>And we care because.... ?
>
>We care because we like helping people who have Slacware questions.

Well thinks to all of you for answering this. I did fix get it fixed,
but did it by reinstalling. I must have messed up the basic libs
somehow, and caused this peculiar behavior. Because after
a fresh install, it's all working fine.

After many attempts to see what was causing the difference,
I was still perplexed. The only other time I've seen "unexplained
behavior" like this was when I tried to upgrade my glibc, and it
didn't take properly.

It's a time thing, a half hour to reinstall...days to track down.
Gotta be practical.

On the other hand, I did learn alot about bash, and how
bash differs berween SuSE and Slackware. Slackware probably
does it the right way, but SuSE has it setup, so that everything is
done in .bashrc.










--
I'm not really a human, but I play one on earth.
http://zentara.net/japh.html