12-07-2016
Thanks for the suggestion. I'd tried to read the manual pages but got rather goggle-eyed, so it is now smack-in-the-face obvious that we've got the order wrong.
I feel a fool for not spotting it
Mind you, I didn't do it in the first place, so it's not too bad.
I will see if I can get this put in sometime and report back.
Kind regards,
Robin
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have suse (SLES 9) machine,I would like to know how to creat a PAM
configure file for ldap authentication and loading it using a "config"
argument to pam_ldap.so
Thanks for your help (0 Replies)
Discussion started by: hassan1
0 Replies
2. UNIX for Dummies Questions & Answers
Hi.
i am on solaris. I have changed pam configuration. Do i need to let pam re-read its configuration again? If so, how can i do it?
ps -ef | grep -i pam, returns no hits.
Rgds (0 Replies)
Discussion started by: yls177
0 Replies
3. IP Networking
i have the DNS and the web proxy services running on one of my sun machines....the funny thing is clients use the proxy server by addressing it with its IP address only....what i need is to assign it like...proxy.amu.edu.et......
my guess is the problem is the configuration with the DNS ...but i... (2 Replies)
Discussion started by: henokia4j
2 Replies
4. Red Hat
Hi,
I've configured two linux boxes to authenticate against Windows Active Directory using Kerberos while retrieving authorization data (uids, gids ,,,)from NIS.
The problem I ran into with my PAM configuration is that all authentication attempts succeed in order.i.e. if someone tried his... (0 Replies)
Discussion started by: geek.ksa
0 Replies
5. IP Networking
Can any one direct me to the resources where I can find in-depth instructions on Squid Proxy server and its configuration?
Thanks in advance.:) (1 Reply)
Discussion started by: admin_xor
1 Replies
6. UNIX for Advanced & Expert Users
Hello all,
I am trying to configure squid proxy server for different organizations. These organizations will have different blocked ports, different acls, etc. But, I can use only one proxy server for this purpose. Thinking of making a shell script with iptables and squid.
For an example: a... (1 Reply)
Discussion started by: admin_xor
1 Replies
7. Shell Programming and Scripting
This is a weird problem. Following is my code.
/opt/quest/bin/vastool configure pam sshd
/opt/quest/bin/vastool configure pam ssh
cat /etc/pam.conf | \
awk '$1=="ssh"||$1=="sshd"||$1=="emagent"{sub("prohibit","aix",$NF);}1' OFS='\t' > /etc/pam.conf
cat /etc/ssh/sshd_config | \
sed -e... (2 Replies)
Discussion started by: pjeedu2247
2 Replies
8. UNIX for Dummies Questions & Answers
Hello, i setup an open socks proxy on my remote vps:
ssh -f -N -D 0.0.0.0:1080 localhost
and then allowed only connections from IP of my home computer
iptables -A INPUT --src myhomeip -p tcp --dport 1080 -j ACCEPT
iptables -A INPUT -p tcp --dport 1080 -j REJECT
but it appears that im... (3 Replies)
Discussion started by: postcd
3 Replies
9. Shell Programming and Scripting
I have a list of ip socks / port(eg: 192.168.0.1 80). I would like to write a bash to test automatically these addresses in a loop with firefox. The problem is that firefox process stays alive even when firefox does not work because of wrong network settings. So I want to kill the process when the... (3 Replies)
Discussion started by: arpagon
3 Replies
LEARN ABOUT DEBIAN
yodlmanpage
yodlmanpage(7) Your Own Document Language yodlmanpage(7)
NAME
yodlmanpage - Yodl's `manpage' document type
SYNOPSIS
The manpage document type was specifically implemented to write Unix-style manual pages. Other Yodl document formats, such as article,
report and book are documented in the Yodl guide and in the manpage for yodlmacros.
DESCRIPTION
This manual page briefly describes the manpage document type of the YOLD document language. This document type is specific enough that it
warrants a separate manpage.
manpage documents do not use the `standard' sectioning commands (e.g., sect() and subsect()), but have specific manpage...() macros. You
can however use (and are encouraged to..) other `normal' macros, such as description(...) or itemization(...) for lists, or bf() for bold-
face and em() for emphasis. As for fonts, the following is suggested:
o Use em(text) when text is a variable, or a placeholder, etc..
o Use bf(text) when text is literal, such as a command, a filename, a directory. Each manpage document in Yodl must be organized as
follows:
o manpage(name) (section) (date) (package) (source): This is the preamble of the document. It states whatever the page describes, the
section where it belongs, the release date, the package that it belongs to, and the source of the package. The section number
should be (according to the Linux manpage on man): 1 for commands, 2 for system calls, 3 for library calls, 4 for special files, 5
for file formats, 6 for games, 7 for macro packages and conventions, 8 for system management commands, and 9 for other special sub-
jects (e.g., kernel commands).
o manpagename(name) (short description): The name is again whatever is described, the short description is what e.g., the whatis
database uses for descriptions.
o manpagesynopsis(): a very short `usage' information or similar. Keep this section short, e.g., a line with all program options is
acceptable but without descriptions (these come later).
o manpagedescription(): the purpose of the program and such. This is also the place to document the workings.
o manpageoptions(): This is the place to document e.g. the flags that are stated in the manpagesynopsis(). This section is optional,
but when present, must appear at this place.
o manpagefiles(): relevant files are described in this section.
o manpageseealso(): this section lists related manual pages.
o manpagediagnostics(): Error conditions, error messages, etc..
o manpagebugs(): This is where known bugs are described. This section is optional.
o manpageauthor(): stating the author and/or the maintainer.
o manpagesection(NAME): This macro starts a generic, non-required section. E.g., you might want a manpagesection(EXAMPLES) in your
document. As a typographic suggestion, use upper case for the NAME argument for consistency reasons.
SEE ALSO
yodlstriproff(1), yodl(1), yodlbuiltins(7), yodlconverters(1), yodlletter(7), yodlmacros(7), yodlpost(1), yodlverbinsert(1).
BUGS
-
AUTHOR
Frank B. Brokken (f.b.brokken@rug.nl),
yodl_3.00.0.tar.gz 1996-2010 yodlmanpage(7)