matt zagrabelny, 2003-Mar-07 09:16 -0600:
> i am currently stopping wvdial with:
>
> killall wvdial
>
> sometimes the permissions to /dev/modem (/dev/ttyS0)
> which are usually "root dialout -rw-rw"
> do not get reset to this.
>
> i know that when pppd is running that it removes
> group "rw"
i am currently stopping wvdial with:
killall wvdial
sometimes the permissions to /dev/modem (/dev/ttyS0)
which are usually "root dialout -rw-rw"
do not get reset to this.
i know that when pppd is running that it removes
group "rw" to the device, effectively making the permissions
"600", and
Wade Barocsi writes:
> I have been using wvdial without difficulty for weeks. Upon use this
> evening, I am getting "permission denied cannot open /dev/ttyS2". Any
> Idea on why this has changed?
A known bug in wvdial. The port should be group writeable. Just change it
back.
> wvdial works fin
I have been using wvdial without difficulty for weeks. Upon use this evening, I
am getting "permission denied cannot open /dev/ttyS2". Any Idea on why this
has changed? No one has made any (known)changes.
What should /dev/ttyS2 permissions be on a standalone desktop system?
ls -l:cr
On Sat, 3 Apr 1999, Chris Mayes wrote:
> This means that the dialout group can read it, right? So, I did this to
> the dialout line of /etc/group:
> dialout:x:20:cmayes:
close:
dialout:x:20:cmayes
you would separate users by commas if you had more than one in that group.
the 'adduser' command
I always end up doing horrible, insecure hacks in order to access the
wvdial stuff, and since I am now using wvdial's "home distribution, I'd
like to do it properly. Here's the current error:
cmayes:~$ wvdial
--> Can't read config file: Permission denied
Here's the config file's permissions:
-rw
6 matches
Mail list logo
