Rob van der Putten <r...@sput.nl> writes: > Hi there > > > Rob wrote: > >> So do a "stty -a </dev/refclock-0" the next time it is messed up again. >> Then you should get this output: >> speed 50 baud; rows 0; columns 0; line = 0; >> intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = >> <undef>; >> eol = <undef>; eol2 = <undef>; swtch = <undef>; start = <undef>; stop = >> <undef>; >> susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>; >> flush = <undef>; min = 1; time = 0; >> parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts >> -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon >> -ixoff >> -iuclc -ixany -imaxbel -iutf8 >> -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 >> vt0 ff0 >> -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop >> -echoprt >> -echoctl -echoke >> If not, something has messed up your port. Your task to find out >> what >> it is. > > Assuming of course, that ntpd doesn't reset the tty to the original > values when stopped. > Or should I do this with ntpd running?
You should do it with ntpd running, otherwise the port will most likely be reset to the default values by the OS when the port is closed. > > > Regards, > Rob _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
