Bug 7215 - linuconf corrupted /etc/smb.conf file
linuconf corrupted /etc/smb.conf file
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-22 00:19 EST by Laurent Chavey
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-12-15 16:02:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Laurent Chavey 1999-11-22 00:19:11 EST
While tryning to configure samba using linux conf, after
quite a bit off trying different config to connect to a
NT4.1 ws patch 3.0, I got my /etc/smb.conf file corrupted.
(the file was still readable, but a lot of garbage was addded to
it)

:-))
Comment 1 jack 1999-11-23 11:53:59 EST
This was reported once on the linuxconf mailing list, but we can't replicate it.
Comment 2 Anonymous 1999-11-26 14:59:59 EST
I have exactly the same problem with
linuxconf at RedHat 6.0 and 6.1
Eventually, linuxconf will corrupt /etc/smb.conf
I can not give exact sequence of keys to be pressed,
but every time after some extensive
configuration work linuxconf corrupts the /etc/smb.conf
I had this problem three times, since then
I do not use linuxconf for configuration any more.
Linuxconf either crashes (much more often when used with
grome frontend), or corrupts the files.
If you want I can try to reproduce the problem
with /etc/smb.conf again.
Comment 3 Dale Lovelace 1999-12-03 14:50:59 EST
I can't reproduce this with linuxconf-1.16r10. This will be released as errata
when testing is completed. I suggest upgrading when it is available.
Comment 4 Michael K. Johnson 1999-12-15 16:02:59 EST
1.16r10-2 released

Note You need to log in before you can comment on or make changes to this bug.