>>>
>>>
>>> Unfortunately you can't do that if you log to the SAME volume you are
>>> suspending - i.e. you run your command from your root volume
>>> which is also suspended.
>>>
>>> We could likely 'buffer' the output while in suspend mode,
>>> and throw out the output later - but as
Dne 20.2.2016 v 14:25 Lentes, Bernd napsal(a):
- Am 19. Feb 2016 um 21:31 schrieb Zdenek Kabelac zdenek.kabe...@gmail.com:
Dne 19.2.2016 v 19:40 Lentes, Bernd napsal(a):
Hi,
i have a script in which i invoke lvremove and lvcreate. With lvremove i don't
have proplems but with lvcreate.
- Am 19. Feb 2016 um 21:31 schrieb Zdenek Kabelac zdenek.kabe...@gmail.com:
> Dne 19.2.2016 v 19:40 Lentes, Bernd napsal(a):
>> Hi,
>>
>> i have a script in which i invoke lvremove and lvcreate. With lvremove i
>> don't
>> have proplems but with lvcreate.
>> I'm redirecting stdout and
> 20 февр. 2016 г., в 1:31, Zdenek Kabelac
> написал(а):
>
> Dne 19.2.2016 v 19:40 Lentes, Bernd napsal(a):
>> Hi,
>>
>> i have a script in which i invoke lvremove and lvcreate. With lvremove i
>> don't have proplems but with lvcreate.
>> I'm redirecting stdout and
Dne 19.2.2016 v 19:40 Lentes, Bernd napsal(a):
Hi,
i have a script in which i invoke lvremove and lvcreate. With lvremove i don't
have proplems but with lvcreate.
I'm redirecting stdout and stderr to a file because the script is executed by
cron and i'd like to have a look afterwards if