Red Hat Bugzilla – Bug 50889
running neat from the /etc/sysconfig/networking/profiles/default directory makes the directory inaccessible
Last modified: 2015-03-04 20:09:25 EST
Description of Problem:
If you run neat from the "default" directory, it makes the directory
inaccesible (ls returns nothing, attempts to write the directory fail).
Sometimes, the problem is accompanied by this error:
shell-init: could not get current directory: getcwd: cannot access parent
directories: No such file or directory
the error occurs sometimes when programs try to access the directory, and
sometimes is output by neat as it closes.
Steps to Reproduce:
1. run neat from the /etc/sysconfig/networking/profiles/default
2. exit neat
3. Note the errors, ls can't list the directory, etc.
4. recover by backing out of the directory and then going back in.
directory is inaccessible
neat should not have an effect on any directory, although this one seems to
be special (the problem only occurs in this directory) -- it may not be
neat causing the problem, it might be something in the shell responding to
a command issued by neat.
The profile system is currently being adjusted.
This happens because when you press the OK button the configuration directory
/etc/sysconfig/networking/profiles will be recreated.
The problem is that it is not know wether new profiles had been added by hand
while neat was running, so we basically have to recreate the subdirectories there.
Agreed, default could stay, but all others need to be recreated.
Everything else leads to extreme madness.
I will fix it sothat it won't touch the default profile as that has to be always
Read ya, Phil
This defect is considered SHOULD-FIX for Fairfax.
Fixed in CVS.