dear bud,
>
> Do a chmod 777 /var/lock while logged in as root. Also make sure that
> there isn't a "stale" lock file in there already that you can't over right.
sorry, but i am not very used to work in console, even if i wanna
learn it. so i typed 777 /var/lock as root but nothing happened.
> Say if you used minicom while as root, it crashed out, left the lock file owned by
>root, and now "normal user" can't overwrite the file, since he doesn't have
> premission.
i dont understand this one...
> I forgot the lock files name, but do a ls in that directoy and
> see if anything "looks" like a modem lock file. If there is, become root
> and rm it. Then try again.
so, i typed ls and did get:
chap secrets ip-down ip-up options pap-secrets
and here maybe it is important to say that ip-down and ip-up was
written in green...
mek
>
>> dear newbies,
>> on my redhat 60 machine i did setup kppp(a kde feature) under
>> gnome what did work fine. but finally when i tried to dial in i
did
>> get the answer "can't create modem lock file" so i couldnt make a
>> connection. i asked a friend of mine and he said that i have to
>> delete /etc/ppp/options what i did, and after i get the same
>>message. in kppp-help i read the frequently asked questions and
>> indeed the third most frequently asked question was this one.
there
>> i get the hint to make sure that /var/lock/ should be read-wirte
>> mode for any user and i also did this. what did'nt change the
>> situation of making a connection to the internet. somebody maybe
had >> the same problem once? >> >> mek
>
