u/Alarmed-Prize-7500

SOLVED

Solution:

Add these lines to "~/.profile":

if [  "$SHELL" == "/bin/sh" -a -x /bin/bash ]; then
    export SHELL=/bin/bash
    exec /bin/bash --login
fi

if [ "$BASH" ] ; then source ~/.bashrc ; fi

Create file "~/.bashrc" if it doesn't exist

Add these lines to "~/.bashrc":

HISTFILE=~/.bash_history

Run commands:

source ~/.bashrc
source ~/.profile

Restart NAS

==================================

Hello. I'm using a Synology NAS, and I'm trying to make it so my bash commands history stays there even after restarts or updates. Currently, the bash commands history gets cleared when the system restarts.

I read that running "bash --login" can create the ".bashrc" and ".bash_history" files, so I ran it on the NAS via SSH with my user, but it didn't create the files.

When I run "echo $HISTFILE", it returns "/var/tmp/.bash_history", but running "ls -ap /var/tmp/" doesn't show a ".bash_history" anywhere in that directory. Plus, the "/var/tmp/" directory gets cleared everytime the system restarts, so if it actually is there somehow, then it's a bad place for it to be anyway.

I also read that "/etc.defaults/" has a ".bashrc_profile" file that stays there even after the system restarts and updates, although I'm not sure how I'm supposed to use that info at the moment.

How do I create the ".bashrc" and ".bash_history" files, and have them stay on the system after restarting and updating?

SOLVED

Solution:

Add these lines to "~/.profile":

if [  "$SHELL" == "/bin/sh" -a -x /bin/bash ]; then
    export SHELL=/bin/bash
    exec /bin/bash --login
fi

if [ "$BASH" ] ; then source ~/.bashrc ; fi

Create file "~/.bashrc" if it doesn't exist

Add these lines to "~/.bashrc":

HISTFILE=~/.bash_history

Run commands:

source ~/.bashrc
source ~/.profile

Restart NAS

==================================

Hello. I'm using a Synology NAS, and I'm trying to make it so my bash commands history stays there even after restarts or updates. Currently, the bash commands history gets cleared when the system restarts.

I read that running "bash --login" can create the ".bashrc" and ".bash_history" files, so I ran it on the NAS via SSH with my user, but it didn't create the files.

When I run "echo $HISTFILE", it returns "/var/tmp/.bash_history", but running "ls -ap /var/tmp/" doesn't show a ".bash_history" anywhere in that directory. Plus, the "/var/tmp/" directory gets cleared everytime the system restarts, so if it actually is there somehow, then it's a bad place for it to be anyway.

I also read that "/etc.defaults/" has a ".bashrc_profile" file that stays there even after the system restarts and updates, although I'm not sure how I'm supposed to use that info at the moment.

How do I create the ".bashrc" and ".bash_history" files, and have them stay on the system after restarting and updating?

My battery backup had an "Overload Shutdown", where the power LED was off and it made a constant long beep noise. It happened out of nowhere, and the battery backup had been running fine for a while. The only thing that was plugged into it was my NAS, so I'm wondering how the battery backup even had an "Overload Shutdown" in the first place.

The battery backup is BE600M1, and the NAS is a Synology NAS DS923+.

I read online that the long beep on battery backups means the wattage of the devices connected to the NAS exceeded the capacity of the battery backup, but that doesn't make sense, because the only device I have plugged into the battery backup uses less watts than the battery backup uses.

The DS923+ has an input power of 100-240V, 50-60 Hz, and maximum power consumption is 37.91 W. The Battery Backup is 600VA/330W, which means it supports more volts and watts than the one device I had plugged into it.

My battery backup had an "Overload Shutdown", where the power LED was off and it made a constant long beep noise. It happened out of nowhere, and the battery backup had been running fine for a while. The only thing that was plugged into it was my NAS, so I'm wondering how the battery backup even had an "Overload Shutdown" in the first place.

The battery backup is BE600M1, and the NAS is a Synology NAS DS923+.

I read online that the long beep on battery backups means the wattage of the devices connected to the NAS exceeded the capacity of the battery backup, but that doesn't make sense, because the only device I have plugged into the battery backup uses less watts than the battery backup uses.

The DS923+ has an input power of 100-240V, 50-60 Hz, and maximum power consumption is 37.91 W. The Battery Backup is 600VA/330W, which means it supports more volts and watts than the one device I had plugged into it.

My battery backup had an "Overload Shutdown", where the power LED was off and it made a constant long beep noise. It happened out of nowhere, and the battery backup had been running fine for a while. The only thing that was plugged into it was my NAS, so I'm wondering how the battery backup even had an "Overload Shutdown" in the first place.

The battery backup is BE600M1, and the NAS is a Synology NAS DS923+.

I read online that the long beep on battery backups means the wattage of the devices connected to the NAS exceeded the capacity of the battery backup, but that doesn't make sense, because the only device I have plugged into the battery backup uses less watts than the battery backup uses.

The DS923+ has an input power of 100-240V, 50-60 Hz, and maximum power consumption is 37.91 W. The Battery Backup is 600VA/330W, which means it supports more volts and watts than the one device I had plugged into it.