LinuxQuestions.org - Webfs - cannot change document root

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - Webfs - cannot change document root (https://www.linuxquestions.org/questions/linux-software-2/webfs-cannot-change-document-root-4175667463/)

Webfs - cannot change document root

Code:

#uname -a

Linux fir.nuclix 5.3.0-3parrot3-amd64 #1 SMP Parrot 5.3.9-3parrot3 (2019-11-23) x86_64 GNU/Linux

Code:

#webfsd -h

-r dir  document root is >dir< 



#webfsd -r ~/webdocs

bind: Address already in use

Code:

# vim /etc/webfsd.conf



# document root

web_root="/home/myhomedir/webdocs"



#service webfs stop

#service webfs start

Fails again. It still uses /var/www/html as the document root.

Any ideas?

Did you restart webfs after changing its configuration?

> Did you restart webfs after changing its configuration?

Yes.

Code:

# vim /etc/webfsd.conf



# document root

web_root="/home/myhomedir/webdocs"



#service webfs stop

#service webfs start

Are you sure the service isn't webfsd?

What does service webfs status show before and after the restart?
What does service webfsd status show?

Quote:

Originally Posted by walterbyrd (Post 6077201)

> Did you restart webfs after changing its configuration?

Yes.

Code:

# vim /etc/webfsd.conf



# document root

web_root="/home/myhomedir/webdocs"



#service webfs stop

#service webfs start

Oh, I see.
That was supposed to be command line output. It looked like part of /etc/webfsd.conf to me.
Anyhow, I'm pretty sure ParrotOS uses systemd, so you might try using 'systemctl start/stop/restart ...'.
Along with 'systemctl status ...'.
Another aspect is the OS itself - who knows what it does to avoid being abused as a web server?
And you completely ignored the 'bind: ' message, no? Which 'bind' is this about - the shell builtin or the DNS server? webfs does not depend on bind on my system.

With the hints & info you got so far, I hope you can get a little more proactive in troubleshooting your problem now.

Thank you for the replay. I think I will switch to apache2. It is better known.

Thanks again.