Empty file called 'sudo' in home directory
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I have encountered empty file just called 'sudo' in home directory. The file size is 0 bytes. Is it safe to just delete this file?
sudo opensuse
asked Nov 10 '17 at 8:08
Pekov
1425
add a comment |Â
up vote
3
down vote
favorite
I have encountered empty file just called 'sudo' in home directory. The file size is 0 bytes. Is it safe to just delete this file?
sudo opensuse
asked Nov 10 '17 at 8:08
Pekov
1425
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have encountered empty file just called 'sudo' in home directory. The file size is 0 bytes. Is it safe to just delete this file?
sudo opensuse
asked Nov 10 '17 at 8:08
Pekov
1425
I have encountered empty file just called 'sudo' in home directory. The file size is 0 bytes. Is it safe to just delete this file?
sudo opensuse
asked Nov 10 '17 at 8:08
Pekov
1425
asked Nov 10 '17 at 8:08
Pekov
1425
asked Nov 10 '17 at 8:08
Pekov
1425
asked Nov 10 '17 at 8:08
Pekov
1425
1425
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
5
down vote
accepted
Yes, that's not a system file. It was probably created by mistake. Check its owner and creation date, that'll tell you more about it.
You can safely delete it. At worst, you can recreate it via the command touch ~/sudo.
Config files and other system files usually start with a dot (.). These are the so-called dotfiles, and you should not touch them unless you know what you're doing.
answered Nov 10 '17 at 8:12
dr01
15.3k114769
add a comment |Â
up vote
2
down vote
It would be weird if this file served any regular purpose. You can add to your question the output of your shell history filtered for sudo if it's not too long, and it should be clear where the file came from. The command to get that is
history | grep sudo
There's a good chance the file was created not from your shell though. If the ownership is root you can run the same command from root.
answered Nov 10 '17 at 16:53
Tomasz
8,05052560
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
Yes, that's not a system file. It was probably created by mistake. Check its owner and creation date, that'll tell you more about it.
You can safely delete it. At worst, you can recreate it via the command touch ~/sudo.
Config files and other system files usually start with a dot (.). These are the so-called dotfiles, and you should not touch them unless you know what you're doing.
answered Nov 10 '17 at 8:12
dr01
15.3k114769
add a comment |Â
up vote
5
down vote
accepted
Yes, that's not a system file. It was probably created by mistake. Check its owner and creation date, that'll tell you more about it.
You can safely delete it. At worst, you can recreate it via the command touch ~/sudo.
Config files and other system files usually start with a dot (.). These are the so-called dotfiles, and you should not touch them unless you know what you're doing.
answered Nov 10 '17 at 8:12
dr01
15.3k114769
add a comment |Â
up vote
5
down vote
accepted
up vote
5
down vote
accepted
Yes, that's not a system file. It was probably created by mistake. Check its owner and creation date, that'll tell you more about it.
You can safely delete it. At worst, you can recreate it via the command touch ~/sudo.
Config files and other system files usually start with a dot (.). These are the so-called dotfiles, and you should not touch them unless you know what you're doing.
answered Nov 10 '17 at 8:12
dr01
15.3k114769
Yes, that's not a system file. It was probably created by mistake. Check its owner and creation date, that'll tell you more about it.
You can safely delete it. At worst, you can recreate it via the command touch ~/sudo.
Config files and other system files usually start with a dot (.). These are the so-called dotfiles, and you should not touch them unless you know what you're doing.
answered Nov 10 '17 at 8:12
dr01
15.3k114769
edited Nov 10 '17 at 8:18
answered Nov 10 '17 at 8:12
dr01
15.3k114769
answered Nov 10 '17 at 8:12
dr01
15.3k114769
answered Nov 10 '17 at 8:12
dr01
15.3k114769
15.3k114769
add a comment |Â
add a comment |Â
up vote
2
down vote
It would be weird if this file served any regular purpose. You can add to your question the output of your shell history filtered for sudo if it's not too long, and it should be clear where the file came from. The command to get that is
history | grep sudo
There's a good chance the file was created not from your shell though. If the ownership is root you can run the same command from root.
answered Nov 10 '17 at 16:53
Tomasz
8,05052560
add a comment |Â
up vote
2
down vote
It would be weird if this file served any regular purpose. You can add to your question the output of your shell history filtered for sudo if it's not too long, and it should be clear where the file came from. The command to get that is
history | grep sudo
There's a good chance the file was created not from your shell though. If the ownership is root you can run the same command from root.
answered Nov 10 '17 at 16:53
Tomasz
8,05052560
add a comment |Â
up vote
2
down vote
up vote
2
down vote
It would be weird if this file served any regular purpose. You can add to your question the output of your shell history filtered for sudo if it's not too long, and it should be clear where the file came from. The command to get that is
history | grep sudo
There's a good chance the file was created not from your shell though. If the ownership is root you can run the same command from root.
answered Nov 10 '17 at 16:53
Tomasz
8,05052560
It would be weird if this file served any regular purpose. You can add to your question the output of your shell history filtered for sudo if it's not too long, and it should be clear where the file came from. The command to get that is
history | grep sudo
There's a good chance the file was created not from your shell though. If the ownership is root you can run the same command from root.
answered Nov 10 '17 at 16:53
Tomasz
8,05052560
answered Nov 10 '17 at 16:53
Tomasz
8,05052560
answered Nov 10 '17 at 16:53
Tomasz
8,05052560
answered Nov 10 '17 at 16:53
Tomasz
8,05052560
8,05052560
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f403697%2fempty-file-called-sudo-in-home-directory%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
