I may be possible to do this via Powershell, and at some point that may be. The point.

But right now, I am trying to prevent people from causing issues going forward with renaming the source folder.

This simple script - Windows Batch file - dos the following;

-Copy shortcut to /users/public/desktop
-Calls install of adobe Reader XI (compatibility issue with newer)
-Calls install of two additional applications.

Since I created it, the path to it has been changed twice... Is there a way to set a variable that grabs the path -

ETA:
I many have answered my own question. Generally the folder is access via Explorer, not CMD. As such, I dont think it can grab the path to the file.

you can get away from home users downloading files to they're personal devices with policy... strict policy and using a VDI instead.

@AshKetchum said in Out of office auto reply best practice:

Hi,
We set up an auto-reply (exchange) for employees that left the company. We then disable their domain account. I assume when we disable the domain account their email is disabled as well and inaccessible.
We noticed that the employee that left the company 6 months ago still has an active auto-reply. what is the best practice and how long should auto-reply for terminated employees?

IT will vary between companies or policies. However in some cases where SSO is used,.. AD and Exchange / read: O365 can be done at once (IIRC). In a number of cases though, disable / move AD account - Forward and terminate the email.

@DustinB3403 said in Linux History: Not clearing between -:

You also could've run history -d linenumber to have removed things that were incorrect or frivolous.

Done that also - didn't do anymore than history -c did.

This has been helpful - I've managed to edit the file, and after making a backup, and editing it down to clear out the garbage.

@jmoore said in Linux History: Not clearing between -:

@gjacobse wouldn't the . be part of the filename though? So it would be "sudo vi /root/.bash_history"

Quite true indeed - so I missed i there,.. but didn't here: 190 sudo nano ~/.bash.history

So - this is my confusion now:

[email protected]:~# echo "$HISTFILE"
/root/.bash_history
[email protected]:~# sudo vi /root/bash_history

~
~
~
~

The listed history file is - well - blank. But obviously - it isn't as it's now 202 lines (default seems to be set to 1000)

Incidently - when I do execute the history -c it clears - but when i re-connect it is still there.

@EddieJennings said in Linux History: Not clearing between -:

https://eshlox.net/2017/08/01/bash-increase-command-history-size

You'll be decreasing the size instead

I don't know that the size is so much of an issue as the inability of deleting it. Having 200 lines is fine -

@jmoore said in Linux History: Not clearing between -:

@gjacobse I don't remember about -c specifically but I am pretty sure you can go to your bash profile and set the amount of history you want to keep.

I haven't spent any time in the bash profile. so I will look into this. Right after this call should have been an email

@EddieJennings said in Linux History: Not clearing between -:

@gjacobse said in Linux History: Not clearing between -:

But it has gotten a bit long on the Ubuntu system I have running.

Is this causing some kind of problem?

Only in the sense that as I have been learning - I've made errors,.. and to prevent continuing those errors, if I clear the hsitory, I can then re-enforce the correct commands. Not to mention I copied some content, and made the mistake of pasting it back into the terminal... resulting in about 20-30 lines of meaningless junk.