Hi All,
Does anyone know if a requirement has been submitted for a decent
cancel command?
I have a couple of issues. The first is when there is a script running
and for whatever reason it is necessary to stop it. Cancelling the
current process just allows the script to start the next one, and
> So, recent unixy clients have changed their behavior w.r.t. logfile
> access; I think I understand (and support) the rationale, but it
> leaves me with a nontrivial sysadmin problem. Or maybe it's just a
> silly squeamishness, I dunno.
>
> The change is that, if the client can't write to the err
Joni,
I'd recommend doing 5.3.0 -> 5.3.4 -> 5.3.4.2.
The licensing changes from 5.2 to 5.3. You'll want to "register lic
file=tsmee.lic".
I assume you're aware of the ISC/AC, and the requirements for that. To
make the transition easier, I'd install the patches for the "classic" web
interface.
So, recent unixy clients have changed their behavior w.r.t. logfile
access; I think I understand (and support) the rationale, but it
leaves me with a nontrivial sysadmin problem. Or maybe it's just a
silly squeamishness, I dunno.
The change is that, if the client can't write to the error log, it
Well, not using documented commands that is...
If you issue the following SQL statement to retrieve the file's object
id:
select * from backups where node_name='' and
filespace_name='\\\$' and
hl_name='\\' and ll_name=''
you can use the command:
Show bfo 0
to retrieve object id of the superbit
