That's the output of a file produced by the nohup program, which is used to run things in the context of a shell, but without the program being killed when the shell is exited. You can delete it if you don't want what's in it, but if the program that created the file is still running, then the disk space won't actually be reclaimed until the program exits.
Also, the chances are that whatever created the file will probably do it again in the future, so you really want to run activemq as a proper daemon, rather than someone logging in and running it in a shell with nohup.
As another idea, you could run it so that there is no output to be placed into nohup.out:
Just start the command like this:
nohup command > /dev/null
This will cause the output from everything to be sent to "/dev/null" and disappear. If you don't care about the logs, this is the easiest way to stop the file from taking up room on the HDD...
That's the output of a file produced by the
nohupprogram, which is used to run things in the context of a shell, but without the program being killed when the shell is exited. You can delete it if you don't want what's in it, but if the program that created the file is still running, then the disk space won't actually be reclaimed until the program exits.Also, the chances are that whatever created the file will probably do it again in the future, so you really want to run activemq as a proper daemon, rather than someone logging in and running it in a shell with
nohup.As another idea, you could run it so that there is no output to be placed into nohup.out:
Just start the command like this:
This will cause the output from everything to be sent to "/dev/null" and disappear. If you don't care about the logs, this is the easiest way to stop the file from taking up room on the HDD...
you can clear nohup.out by