On Thu, 26 Feb 1998, Aghart wrote:
Hallo-hallo,
saya coba analisa ya.. kalo ada yg salah mohon rekan2x yg lain betulin..
lagian saya juga nggak ngikutin ini dari awal.. jadi kalo ada yg salah,
maklum deh..
> Feb 26 03:42:38 localhost pppd[662]: pppd 2.2.0 started by root, uid 0
> Feb 26 03:42:39 localhost chat[663]: timeout set to 3 seconds
Saya sih pake timeout 30 detik (emang kelamaan sih..), soalnya kalo 3
detik kayaknya terlalu cepat deh.. kalo belum handshake dg modem yg ada di
seberang dlm jangka waktu 3 detik, chatnya nanti dapet alarm..
> Feb 26 03:42:39 localhost chat[663]: abort on (\nBUSY\r)
> Feb 26 03:42:39 localhost chat[663]: abort on (\nNO ANSWER\r)
> Feb 26 03:42:39 localhost chat[663]: abort on (\nRINGING\r\n\r\nRINGING\r)
> Feb 26 03:42:39 localhost chat[663]: send (rAT^M)
> Feb 26 03:42:39 localhost chat[663]: expect (OK)
> Feb 26 03:42:42 localhost pppd[666]: pppd 2.2.0 started by root, uid 0
> Feb 26 03:42:42 localhost pppd[666]: Device ttyS0 is locked by pid 662
^^^^^ ^^^
/dev/ttyS0 kan biasanya dipake buat mouse ya (COM1), kalo modem biasanya
di COM2 ( ttyS1 atau cua1 ).
Tapi yg saya heran, kok sampe ada multiple pppd yg nyala ya... pppd yg
pidnya 662 belum selesai, kok dalam hanya waktu 4 detik udah ada pppd baru
yg nyala (pid 666). Mungkin ada yg salah di scriptnya ?
> Feb 26 03:42:42 localhost pppd[666]: Exit.
> Feb 26 03:42:42 localhost chat[663]: alarm
^^^^^
Kalo memang salah port,masuk akal kalo chat sampe dapet alarm, soalnya gak
dapet jawaban dari sang modem..
> Feb 26 03:42:42 localhost chat[663]: send (+++)
> Feb 26 03:42:42 localhost chat[663]: expect (OK)
> Feb 26 03:42:45 localhost chat[663]: alarm
> Feb 26 03:42:45 localhost pppd[662]: Connect script failed
> Feb 26 03:42:45 localhost pppd[662]: Exit.
> Feb 26 03:42:45 localhost chat[663]: Failed
Nah, ini pppd yg pertama kali nyala udah K.O. ..
> Feb 26 03:43:02 localhost pppd[672]: pppd 2.2.0 started by root, uid 0
> Feb 26 03:43:04 localhost pppd[674]: pppd 2.2.0 started by root, uid 0
Saya rasa emang ada yg salah kali di scriptnya juga [no offense]..
> Feb 26 03:43:04 localhost pppd[674]: Device ttyS0 is locked by pid 672
> Feb 26 03:43:04 localhost pppd[674]: Exit.
[ snip, after many pppd mengeroyok ttyS0 dg semangat 45 (atau 66)]
> Feb 26 03:46:53 localhost dip[717]: DIP: tty_open: /dev/cua0 (3)
> Feb 26 03:46:59 localhost kernel: PPP: ppp line discipline successfully
Lho.. kok dip ikut-ikutan nimbrung.. Apa anda jalankan dengan secara
manual?
> Feb 26 03:49:56 localhost dip[951]: DIP: tty_open: /dev/cua0 (3)
Coba deh portnya yg ada di script tsb diganti dari /dev/ttyS0 ke
/dev/ttyS1 atau /dev/cua1, sama TIMEOUT-nya diganti, misalnya jadi 15
detik.
Kalo boleh... saya juga pengen liat script yg anda pake (ppp-on, dsb).
-- Anto --
-
STOP-LANGGANAN: 'unsubscribe' ke: [EMAIL PROTECTED]
START-LANGGANAN: 'subscribe' ke: [EMAIL PROTECTED]
