quintaq@yahoo.co.uk wrote:
On Sun, 12 Aug 2001 09:33:37 +0200 Juergen Braukmann
wrote: one thought is that you ran SuSEConfig by working on your system. SuSEConfig resets permissions as "granted" in /etc/permissions.[local|secure|...]. If you changed permissions by hand long time back, that might be the problem.
Hi Juergen,
Thanks for that idea. I don't recall ever hand editing any permissions files, but after the permission denied problem with /dev/modem arose I did go back into YAST to check that my user name still had permission to access the modem. Maybe I caused some problems along the way.
(Or, I am completely wrong. Some memory tells me that (re)setting permissions is also called by cron-dayly). It's worth to be looked at anyway.
It had occurred to me that some cron process might be the culprit - because after I sent my first post yesterday the /dev/modem permission denied problem actually recurred. I checked, however, and cannot see anything in my cron setup that would cause it.
Regards,
Geoff
Hi Geoff, it would be hard to find, something called somwhere. I am currently fiddling with a script that calles awk from a pipe no clue what it does... for your problem, /dev/modem is a link to the real modem device (the port the modem is connected to, like /dev/ttyS0). The permissions must be correct for that device. If permissions changed, set it in /etc/permissions.local like it's done in the other permission files. There were also issues to set the dialout user into group dialout, to enable use of the dialer. I do not remember that stuff, I'm on ISDN and refused to reboot for 153 days now to prevent trouble. ;-) Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\