RTP sys admin guide WIP

I have added some info on Remote line printing over TCP/IP,
Neutrino native networking, and Setting up a two-node
network in the RTP sys admin guide work-in-progress. You can
access it from http://support.qnx.com/support/docs/

If anyone wants to comment, give me a shout.

Regards,
Dave.

David P. Whelan, Technical Writer
QNX Software Systems Ltd.        Email: <dwhelan@qnx.com>
Kanata, Ontario  K2M 1W8         (613) 591-0931 ext.180

Hi Dave,

My first comment may be not directly for you, rather for authors of
‘lpd’, but they came to my mind after reading your “admin guide”, so…
when I was fighting with ‘lpd’, I was unable to get what a heck it
wants, i.e. it was running but exiting just after run… after few hours
I decided to read manual on ‘lpd’ from FreeBSD man (since helpviewer
didn’t tell me enough about ‘lpd’…). And there, in FreeBSD man, I
found that without manual creating main spool directory it won’t stay
running (as a deamon). Now, it seems like a good idea (just in case if
the user is real newbie in UNIX world, which is apparently quit often
happen) to add into ‘lpd’ some minor functionality: if it doesn’t find
that main spool directory, it doesn’t exit silently, but rather brings a
message like this

Default main spooling directory /usr/spool/output/lpd/ not found. Create
it manually or point to existing one by .

My second comment goes for content of “printing” section in your doc.
Correct me if I’m wrong, but HP printers are most widely used, so it
might be better to use “HP laserjet printer” case in your docs.
And, now I’m going to be selfish, please, don’t forget poor guyz with
PostScript printers - cover their case too :wink:))



Dave Whelan wrote:

I have added some info on Remote line printing over TCP/IP,
Neutrino native networking, and Setting up a two-node
network in the RTP sys admin guide work-in-progress. You can
access it from > http://support.qnx.com/support/docs/

If anyone wants to comment, give me a shout.

Regards,
Dave.

David P. Whelan, Technical Writer
QNX Software Systems Ltd.        Email: > <dwhelan@qnx.com>
Kanata, Ontario  K2M 1W8         (613) 591-0931 ext.180


BR, Andrej

Andrej Timchenko <silpol@yahoo.com> wrote:
: Hi Dave,

: My first comment may be not directly for you, rather for authors of
: ‘lpd’, but they came to my mind after reading your “admin guide”, so…
: when I was fighting with ‘lpd’, I was unable to get what a heck it
: wants, i.e. it was running but exiting just after run… after few hours
: I decided to read manual on ‘lpd’ from FreeBSD man (since helpviewer
: didn’t tell me enough about ‘lpd’…). And there, in FreeBSD man, I
: found that without manual creating main spool directory it won’t stay
: running (as a deamon). Now, it seems like a good idea (just in case if
: the user is real newbie in UNIX world, which is apparently quit often
: happen) to add into ‘lpd’ some minor functionality: if it doesn’t find
: that main spool directory, it doesn’t exit silently, but rather brings a
: message like this

: Default main spooling directory /usr/spool/output/lpd/ not found. Create
: it manually or point to existing one by .

I’ll look into beefing up the docs for lpd in the Utilities Reference.
Thanks for the feedback.


Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

For your reference also Andrej you may want to take a look at the
syslogd utility. This is how almost all tcpip applications log
error or status messages, and if syslogd is running it will log
the error message about the directory not being found.

ron


Previously, Steve Reid wrote in qdn.public.news:

Andrej Timchenko <> silpol@yahoo.com> > wrote:
: Hi Dave,

: My first comment may be not directly for you, rather for authors of
: ‘lpd’, but they came to my mind after reading your “admin guide”, so…
: when I was fighting with ‘lpd’, I was unable to get what a heck it
: wants, i.e. it was running but exiting just after run… after few hours
: I decided to read manual on ‘lpd’ from FreeBSD man (since helpviewer
: didn’t tell me enough about ‘lpd’…). And there, in FreeBSD man, I
: found that without manual creating main spool directory it won’t stay
: running (as a deamon). Now, it seems like a good idea (just in case if
: the user is real newbie in UNIX world, which is apparently quit often
: happen) to add into ‘lpd’ some minor functionality: if it doesn’t find
: that main spool directory, it doesn’t exit silently, but rather brings a
: message like this

: Default main spooling directory /usr/spool/output/lpd/ not found. Create
: it manually or point to existing one by .

I’ll look into beefing up the docs for lpd in the Utilities Reference.
Thanks for the feedback.


Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

In article <90itle$2dv$1@nntp.qnx.com>, stever@qnx.com says…

Andrej Timchenko <> silpol@yahoo.com> > wrote:
: Hi Dave,

: My first comment may be not directly for you, rather for authors of
: ‘lpd’, but they came to my mind after reading your “admin guide”, so…
: when I was fighting with ‘lpd’, I was unable to get what a heck it
: wants, i.e. it was running but exiting just after run… after few hours
: I decided to read manual on ‘lpd’ from FreeBSD man (since helpviewer
: didn’t tell me enough about ‘lpd’…). And there, in FreeBSD man, I
: found that without manual creating main spool directory it won’t stay
: running (as a deamon). Now, it seems like a good idea (just in case if
: the user is real newbie in UNIX world, which is apparently quit often
: happen) to add into ‘lpd’ some minor functionality: if it doesn’t find
: that main spool directory, it doesn’t exit silently, but rather brings a
: message like this

: Default main spooling directory /usr/spool/output/lpd/ not found. Create
: it manually or point to existing one by .

I’ll look into beefing up the docs for lpd in the Utilities Reference.
Thanks for the feedback.


Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

Steve, perhaps an indication on the man page for each IP-based utility that
error messages are in syslog and that syslogd should be running would help.

Dean Douthat <ddouthat@faac.com> wrote:
: Steve, perhaps an indication on the man page for each IP-based utility that
: error messages are in syslog and that syslogd should be running would help.

Done – thanks for the suggestion.


Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

I agree with your comments about lpd, you do have to fight
with it to make it do what you want, but it will succumb in
the end. I did say you have to create the spooling directory
under “Somewhere to store files waiting to be printed” but
I’ll make it plainer that you have to create the spool
directory. I’m working on the way to use spooler to do
remote printing by piping into lpd, that’s even worse but it
too does work–I’m trying to write the procedure up in such
a way as to make it easier to conquer it. I’ve used a .ps
example in the bit on printing to a tcp/ip-enabled printer.

Thanks for your input.

Regards,
Dave.
“Andrej Timchenko” <silpol@yahoo.com> wrote in message
news:3A2CDF37.323D3DF7@yahoo.com

Hi Dave,

My first comment may be not directly for you, rather for
authors of
‘lpd’, but they came to my mind after reading your “admin
guide”, so…
when I was fighting with ‘lpd’, I was unable to get what a
heck it
wants, i.e. it was running but exiting just after run…
after few hours
I decided to read manual on ‘lpd’ from FreeBSD man (since
helpviewer
didn’t tell me enough about ‘lpd’…). And there, in
FreeBSD man, I
found that without manual creating main spool directory it
won’t stay
running (as a deamon). Now, it seems like a good idea
(just in case if
the user is real newbie in UNIX world, which is apparently
quit often
happen) to add into ‘lpd’ some minor functionality: if it
doesn’t find
that main spool directory, it doesn’t exit silently, but
rather brings a
message like this

Default main spooling directory /usr/spool/output/lpd/ not
found. Create
it manually or point to existing one by .

My second comment goes for content of “printing” section
in your doc.
Correct me if I’m wrong, but HP printers are most widely
used, so it
might be better to use “HP laserjet printer” case in your
docs.
And, now I’m going to be selfish, please, don’t forget
poor guyz with
PostScript printers - cover their case too > :wink:> ))



Dave Whelan wrote:

I have added some info on Remote line printing over
TCP/IP,
Neutrino native networking, and Setting up a two-node
network in the RTP sys admin guide work-in-progress. You
can
access it from > http://support.qnx.com/support/docs/

If anyone wants to comment, give me a shout.

Regards,
Dave.

David P. Whelan, Technical Writer
QNX Software Systems Ltd.        Email: > <dwhelan@qnx.com>
Kanata, Ontario  K2M 1W8         (613) 591-0931 ext.180


BR, Andrej