[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Problems restoring database on Mac - unsupported rmdi
From: |
Busser, Jim |
Subject: |
Re: [Gnumed-devel] Problems restoring database on Mac - unsupported rmdir -v |
Date: |
Wed, 6 Nov 2013 18:27:01 +0000 |
line 186
rmdir -v ${WORK_DIR}
in
~/Downloads/gnumed-server.19.0/server/gm-restore_database.sh
-- Jim
On 2013-11-06, at 3:28 AM, Sebastian Hilbert <address@hidden> wrote:
> Hi,
>
> Where in the scripts is rmdir called ?
>
> -v option usually means verbose output. It can be safely removed.
>
> NAME
> rmdir - remove empty directories
>
> SYNOPSIS
> rmdir [OPTION]... DIRECTORY...
>
> DESCRIPTION
> Remove the DIRECTORY(ies), if they are empty.
>
> --ignore-fail-on-non-empty
>
> ignore each failure that is solely because a directory
>
> is non-empty
>
> -p, --parents
> remove DIRECTORY and its ancestors; e.g., 'rmdir -p a/b/c' is
> similar to 'rmdir a/b/c a/b a'
>
> -v, --verbose
> output a diagnostic for every directory processed
>
> --help display this help and exit
>
> --version
> output version information and exit
>
>
> Am Mittwoch, 6. November 2013, 12:00:06 schrieb Sebastian Hilbert:
>> Am Mittwoch, 6. November 2013, 09:14:22 schrieb Busser, Jim:
>>> On Mac OS,
>>>
>>> rmdir
>>>
>>> supports only [-p] for the removal of parent directories
>>>
>>>
>>> https://developer.apple.com/library/mac/documentation/Darwin/Reference/Ma
>>> nP
>>>
>>> ages/man1/rmdir.1.html
>>>
>>> So can the
>>>
>>> -v
>>>
>>> be dispensed with?
>>>
>>> Also, following multiple attempts, I ended up with more than a dozen
>>> working directories all at the root level. Shouldn't such working
>>> directories containing copies of backup files be written inside
>>>
>>> /tmp/
>>>
>>> ??
>>
>> Unless I am wrong (which could be) the files are generated in the directory
>> where you are calling the script from. This might not be the directory where
>> your script is.
>>
>> If you happen to *be* at root level calling a script in another directory
>> likely creates the output in the directory you are in, not where the script
>> is in.
>>
>> Sebastian
>>
>> _______________________________________________
>> Gnumed-devel mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/gnumed-devel
>
>
> _______________________________________________
> Gnumed-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnumed-devel