Here is a little more insight about looking at sbbs logs. If you are running sbbs daemonized
and have LogFacility=User then you could look
at /var/log/user.log and/or user.log.1 there are many ways to look at logs.
I will look into your other questions about gtkmonitor, one
thing I am sure if interferring with some of it's features is that if
you run the board as sudo sbbs and exported SBBSCTRL as your login user then the env is not set correctly,
also if you run sudo gtkmonitor it
will open in your desktop as root so the SBBSCTRL env will not be set correctly. When I get home from work I will look at an easy way around this.
Here is a little more insight about looking at sbbs logs. If you are
running sbbs daemonized
In sbbs.ini I have daemonized as false
and have LogFacility=User then you could look at /var/log/user.log
and/or user.log.1 there are many ways to look at logs.
thank you, and yes I found these logs and had a look in them.
On 2018 Oct 16 07:56:00, you wrote to Mortifis:
Here is a little more insight about looking at sbbs logs. If you are
running sbbs daemonized
In sbbs.ini I have daemonized as false
that's correct... the recommended method is to leave that as "false" and use
the "-d" (IIRC) command line option to daemonize sbbs...
and have LogFacility=User then you could look at /var/log/user.log
and/or user.log.1 there are many ways to look at logs.
thank you, and yes I found these logs and had a look in them.
even with that setting, my ubuntu server doesn't have /var/log/user.log and similar... everything has to be dug out of the main syslog.log file(s)...
)\/(ark
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Arguing with a Moderator in public may be hazardous to your access.
---
* Origin: (1:3634/12.73)
â– Synchronet â– Vertrauen â– Home of Synchronet â– [vert/cvs/bbs].synchro.net
Here is a little more insight about looking at sbbs logs. If you are
running sbbs daemonized
In sbbs.ini I have daemonized as false
that's correct... the recommended method is to leave that as "false"
and use the "-d" (IIRC) command line option to daemonize sbbs...
and have LogFacility=User then you could look at /var/log/user.log
and/or user.log.1 there are many ways to look at logs.
thank you, and yes I found these logs and had a look in them.
even with that setting, my ubuntu server doesn't have /var/log/user.log and similar... everything has to be dug out of the main syslog.log file(s)...
Here is a little more insight about looking at sbbs logs. If you
are running sbbs daemonized
In sbbs.ini I have daemonized as false
that's correct... the recommended method is to leave that as "false"
and use the "-d" (IIRC) command line option to daemonize sbbs...
Okay cool thank you, so how and were in sbbs.ini you do this or daemonize:-d
On 2018 Oct 19 11:45:00, you wrote to me:
Okay cool thank you, so how and were in sbbs.ini you do this or daemonize:-d
you don't... leave sbbs.ini as
----->8 snip 8<-----
[UNIX]
blah
Daemonize=False
blah
----->8 snip 8<-----
and then in your start up script, generally in /etc/init.d, the command line would be something like
----->8 snip 8<-----
-blahblah-
PATH=/bin:/sbin:/usr/bin:/usr/bin
SBBSROOT=/sbbs
DAEMON=$SBBSROOT/exec/sbbs
# Command Line options (e.g. daemonize)
OPTIONS="-d"
-blahblah-
$DAEMON $OPTIONS
----->8 snip 8<-----
I have saved this message so I can go though it and edit were I have
to, and to set it up and will check wiki as well, and this it what I
am looking for,
Thank you for this info.
On 2018 Oct 22 08:31:00, you wrote to me:
I have saved this message so I can go though it and edit were I have
to, and to set it up and will check wiki as well, and this it what I
am looking for,
if you get the script as per the wiki, you don't have to edit anything...
just chown, chmod
and place it in init.d or rc.d directory
depending on your system... there was something else i had to run that created the symlinks to the script in the proper init.X or rc.X directories so that sbbs would run on certain runlevels and be shutdown properly when needed... i don't recall what the command is/was to do
that, though... i had to hunt it down again when i set up this installation :/
Hi mark lewis
On 2018 Oct 22 08:31:00, you wrote to me:
I have saved this message so I can go though it and edit were I have to, and to set it up and will check wiki as well, and this it what I
am looking for,
if you get the script as per the wiki, you don't have to edit anything...
Yes I have got the script of wike
just chown, chmod
just a bit unsure what you want me to do here per commands
and place it in init.d or rc.d directory
okay will do place it in init.d or rc.d directory
IMHO on a Raspberry Pi wouldn't it be easier to just:
sudo nano /etc/systemd/system/sbbs.service
and paste in:
[Unit]
Description=Synchronet BBS
Documentation=man:sbbs
After=network.target
[Service]
Restart=on-failure
EnvironmentFile=-/etc/default/sbbs
ExecStart=/sbbs/exec/sbbs nd
ExecReload=/bin/kill -HUP $MAINPID
User=root
Group=root
[Install]
WantedBy=multi-user.target
save and exit then
sudo systemctl enable sbbs
shut your sbbs -nd process (ps -ef | grep sbbs) or pkill sbbs
(you could 'touch/sbbs/data/shutdown' but that doesn't always kill the processes) then
sudo service start sbbs
now it is running as a service ...
if you want to look at the logs
simply cat /var/log/syslog | less
or if you want to see some specific message (ie QNET-FTP)
cat /var/log/syslog | grep QNET-FTP
Hi Mortifis
shut your sbbs -nd process (ps -ef | grep sbbs) or pkill sbbs
not so mush with this at the moment not using qktmonitor
just sbbs/exec/sbbs and use lowercase q to close its down
so do I have to do the above as well -nd etc if so what the command to do
this or after sbbs/exec/sbbs then q it shound be done
(you could 'touch/sbbs/data/shutdown' but that doesn't always kill the
processes) then
Yep okay with this
sudo service start sbbs
Yep okay with this
now it is running as a service ...
okay cool
if you want to look at the logs
simply cat /var/log/syslog | less
okay cool thank you
or if you want to see some specific message (ie QNET-FTP)
cat /var/log/syslog | grep QNET-FTP
This great thank you.YW
Ian S 2nd Choice Core sbbs Nz
Hi Mortifis
shut your sbbs -nd process (ps -ef | grep sbbs) or pkill sbbs
not so mush with this at the moment not using qktmonitor
just sbbs/exec/sbbs and use lowercase q to close its down
so do I have to do the above as well -nd etc if so what the command to do
this or after sbbs/exec/sbbs then q it shound be done
if you ran sbbs daemonized then there is no where to Q [uit] so finding the process id to kill is needed ... ps -ef | grep sbbs will show the pid so if you wanted to kill -9 you'd have it, or you could just run pkill sbbs, this is by no means graceful, but you will be restarting synchronet right afterwards anyway :-)
Hi Mortifis
so do I have to do the above as well -nd etc if so what the command to do
this or after sbbs/exec/sbbs then q it shound be done
if you ran sbbs daemonized then there is no where to Q [uit] so
finding the process id to kill is needed ... ps -ef | grep sbbs will
show the pid so if you wanted to kill -9 you'd have it, or you could
just run pkill sbbs, this is by no means graceful, but you will be
restarting synchronet right afterwards anyway :-)
(you could 'touch/sbbs/data/shutdown' but that doesn't always kill the processes) then
Yep okay with this
Made a typo, that should be touch /sbbs/ctrl/shutdown
sudo service start sbbs
Yep okay with this
now it is running as a service ...
okay cool
you don't have to worry about all of the run level stuff and
graceful shutdowns, as a service the system knows how to be gentle on processes :-)
depending on your system... there was something else i had to run that
created the symlinks to the script in the proper init.X or rc.X
directories so that sbbs would run on certain runlevels and be
shutdown properly when needed... i don't recall what the command
is/was to do that, though... i had to hunt it down again when i set up
this installation :/
okay thank you for hunt it down to created the symlinks to the script
in the proper init.X or rc.X.
if you want to look at the logs simply
cat /var/log/syslog | less
or if you want to see some specific message (ie QNET-FTP) cat /var/log/syslog | grep QNET-FTP
On 2018 Oct 24 17:41:28, you wrote to Sneaky:
if you want to look at the logs simply
cat /var/log/syslog | less
why use cat and pipe the output to less when
less /var/log/syslog
works perfectly? or
tail -F /var/log/syslog
to follow the log? i also provided a quick script previously (monitor_sbbs) which only shows synchronet entries so you have all the normal system log stuff
to wade through...
or if you want to see some specific message (ie QNET-FTP) cat /var/log/syslog | grep QNET-FTP
again with cat :)
egrep -e "QNET-FTP" /var/log/syslog
cat /var/log/syslog | less
why use cat and pipe the output to less when
less /var/log/syslog
works perfectly? or
tail -F /var/log/syslog
tail doesn't give much output
again with cat :)
egrep -e "QNET-FTP" /var/log/syslog
so, it's true, there's more than one way to skin a cat :-P
seems sneaky has many options available to choose from :)
okay thank you for hunt it down to created the symlinks to the script
in the proper init.X or rc.X.
looking through my .bash_history file, it appears that this is the
command i used...
sudo update-rc.d sbbs enable 2 3 4 5
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 04:02:07 |
Calls: | 508 |
Messages: | 219940 |