On Mon, May 31, 2004 at 01:50:10PM +0200, <email address hidden> wrote:
> Package: samba
> Version: 3.0.4-2.backports.org.1
> Severity: normal
Version: 3.0.4-5
Distribution: sid
> i have samba shares on separate fs mount in /var/samba
> postinstall script remove directories to /var/lib/samba
I've the same problem, since /var/samba reflects the same idea of
/var/www, it's seems to me the best place where mounting samba volumes
partitions.
Hint:
- look for some files in /var/samba you expect being there before
moving data to /var/lib/samba/
- write what you're trying to do to the user (he usually is a sysadmin,
he really cares about it) and let him stop/skip the process
- not move _all_ the files in /var/samba if you're not sure of what it
contains
- don't try to simply remove dir, check errors (maybe it's a mounting
point)
Note:
- the current postinst operation may lead to data loss (or leave data in
a messy state), so I'll modify Severity to grave.
I don't think the severity change is a problem, since it's really easy
to fix with some careful file checking, and the current state isn't
acceptable for a sarge release.
On Mon, May 31, 2004 at 01:50:10PM +0200, <email address hidden> wrote: backports. org.1
> Package: samba
> Version: 3.0.4-2.
> Severity: normal
Version: 3.0.4-5
Distribution: sid
> i have samba shares on separate fs mount in /var/samba
> postinstall script remove directories to /var/lib/samba
I've the same problem, since /var/samba reflects the same idea of
/var/www, it's seems to me the best place where mounting samba volumes
partitions.
Hint:
- look for some files in /var/samba you expect being there before
moving data to /var/lib/samba/
- write what you're trying to do to the user (he usually is a sysadmin,
he really cares about it) and let him stop/skip the process
- not move _all_ the files in /var/samba if you're not sure of what it
contains
- don't try to simply remove dir, check errors (maybe it's a mounting
point)
Note:
- the current postinst operation may lead to data loss (or leave data in
a messy state), so I'll modify Severity to grave.
I don't think the severity change is a problem, since it's really easy
to fix with some careful file checking, and the current state isn't
acceptable for a sarge release.
thanks!,
cosimo.