David Wright writes:
> I think the problem when using wvdial is simply that the latter is too
> impatient. Wvdial claims that is sends SIGTERM to pppd, waits 2 seconds
> and then sends SIGKILL.
Please file a bug agains wvdial. Pppd quite often takes quite a while to
shut down: for example, my ISP
Quoting Bob Hilliard ([EMAIL PROTECTED]):
> Hugo van der Merwe <[EMAIL PROTECTED]> writes:
>
> > Something on my machine is periodically changing /dev/ttyS0's
> > permissions to 640, whereas it needs to be 660 to use the modem
>
> ppp changes the permissions to 640 on the device it is using,
also sprach Bob Hilliard (on Wed, 07 Feb 2001 02:52:22PM -0500):
> ppp changes the permissions to 640 on the device it is using, and
> restores them when it exits. If it exits abnormally (crash, kill -9,
> etc) the permissions are not restored. I have suspected that it does
> not always rest
Hugo van der Merwe <[EMAIL PROTECTED]> writes:
> Something on my machine is periodically changing /dev/ttyS0's
> permissions to 640, whereas it needs to be 660 to use the modem
ppp changes the permissions to 640 on the device it is using, and
restores them when it exits. If it exits abnorma
Quoting Hugo van der Merwe ([EMAIL PROTECTED]):
> Something on my machine is periodically changing /dev/ttyS0's
> permissions to 640, whereas it needs to be 660 to use the modem... I
> have now switched back to using ttyS1, but on laptops with only one
> serial port this is not an option, so I'm s
Hello,
Something on my machine is periodically changing /dev/ttyS0's
permissions to 640, whereas it needs to be 660 to use the modem... I
have now switched back to using ttyS1, but on laptops with only one
serial port this is not an option, so I'm still wondering what it is
that does this. I also
Hello,
I use wmppp to start and stop my ppp-connexion.
Everything works well, but sometimes I have problems with my permissions
on /dev/ttyS0 (my modem) that are changed.
I'm obliged to do a chmod g+rw /dev/ttyS0 to reconfigure my permissions.
my starting script is : wvdial
my stopping script is :
Something else that may be relevant to this thread is mgetty.conf. Mine
certainly messes with /dev/ttySx.
# use these options to make the /dev/tty-device owned by "uucp.uucp"
# and mode "rw-rw-r--" (0664). *LEADING ZERO NEEDED!*
port-owner uucp
port-group uucp
# port-owner dialout
# port-group
What are the permissions on /dev/ttyS0 ?
===
In any war, the first casualty is the truth.
--anon
On Wed, 29 Apr 199
On Wed, 29 Apr 1998, Bob Hilliard wrote:
> /dev/ttyS0 should have 660 permissions. I frequently find my
> /dev/ttyS1 has changed to 640. This can be caused by pppd terminating
> abnormally, and perhaps by other events.
Is there some place in the documentation where one can see what the
per
On Wed, Apr 29, 1998 at 11:14:06PM -0400, Bob Hilliard wrote:
> > > /dev/ttyS0 should have 660 permissions. I frequently find my
> > > /dev/ttyS1 has changed to 640. This can be caused by pppd terminating
> > > abnormally, and perhaps by other events.
> >
> > I knew it, I knew it, I knew it
"Rev. Joseph Carter" <[EMAIL PROTECTED]> wrote:
> > /dev/ttyS0 should have 660 permissions. I frequently find my
> > /dev/ttyS1 has changed to 640. This can be caused by pppd terminating
> > abnormally, and perhaps by other events.
>
> I knew it, I knew it, I knew it! heh
>
> Sounds like
On Thu, 30 Apr 1998, Rev. Joseph Carter wrote:
> On Wed, Apr 29, 1998 at 08:40:35PM -0400, Bob Hilliard wrote:
> > /dev/ttyS0 should have 660 permissions. I frequently find my
> > /dev/ttyS1 has changed to 640. This can be caused by pppd terminating
> > abnormally, and perhaps by other even
On Wed, Apr 29, 1998 at 08:40:35PM -0400, Bob Hilliard wrote:
> /dev/ttyS0 should have 660 permissions. I frequently find my
> /dev/ttyS1 has changed to 640. This can be caused by pppd terminating
> abnormally, and perhaps by other events.
I knew it, I knew it, I knew it! heh
Sounds like
/dev/ttyS0 should have 660 permissions. I frequently find my
/dev/ttyS1 has changed to 640. This can be caused by pppd terminating
abnormally, and perhaps by other events.
Bob
--
_
|_) _ |_ Robert D. Hilliard<[EMAIL PROTECTED]>
|_) (_) |_) Palm City, FL USAPGP
Also, if you changed /etc/group which you were logged in you need to log in
afresh in order for the group addition to take affect.
Bob Nielsen wrote:
> I have /dev/ttyS0 shown as belonging to group dialout and have added my
> username to the dialout group, but I get
>
> cannot open /dev/ttyS0: Pe
Did you check 'ls -l /dev/ttyS0' to make sure the group ownership on the file is
not 'dip' rather than 'dialout' (although I think it should be dialout on my
system, debian 1.3.1, it was set up as group dip).
Bob Nielsen wrote:
> I have /dev/ttyS0 shown as belonging to group dialout and have adde
I have /dev/ttyS0 shown as belonging to group dialout and have added my
username to the dialout group, but I get
cannot open /dev/ttyS0: Permission denied
errors with both minicom and efax. I'd rather not run these as root.
Did I miss something?
Bob
Bob Nielsen Interne
18 matches
Mail list logo
