10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
2. Shell Programming and Scripting
Look at the following data file（cou.data） which has four fields separated by tab.
Four fields are country name, land area, population, continent where it belongs.
As for country name or continent name which has two words, two words are separated by space.
(Data are not accurately... (1 Reply)
Discussion started by: chihuyu
1 Replies
3. Shell Programming and Scripting
Hi there,
I'm running into a very weird situation. Let's forget about the purpose of my initial script please. I noticed the bug whatever I'm trying to do.
I'm on an old server running bash 3.1.17.
Say we have the following script :
foo:~# cat /tmp/test
#!/bin/bash
f1() {
local... (9 Replies)
Discussion started by: chebarbudo
9 Replies
4. Shell Programming and Scripting
This really puzzles me. The following code gives me the error 'expr: syntax error' when I try to do multi-line comment using here document
<<EOF
echo "Sum is: `expr $1 + $2`"
EOF
Even if I explicitly comment out the line containing the expr using "#", the error message would still exist... (3 Replies)
Discussion started by: royalibrahim
3 Replies
5. Solaris
Need to find a way to import an LP printers.conf file to CUPS. I have some new Solaris 11.1 boxes that need to have 300 printers added. (0 Replies)
Discussion started by: os2mac
0 Replies
6. UNIX for Advanced & Expert Users
I've posted about this before, but only recently narrowed the problem down to a specific cause.
Ok, first of all, the behavior:
It occurs when autocompletion brings up its list (not when there is only a single option). Basically, if I were to type, say,
cd ~/<TAB>
I would get something... (2 Replies)
Discussion started by: marshaul
2 Replies
7. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
8. Shell Programming and Scripting
Is it normal behavior for a shell script that terminates to terminate its parent shell when executed with the "." option?
For example, if I have the example script (we'll name it ex.sh):
#!/bin/sh
if
then
echo "Bye."
exit 2
fi
And I execute it like this:
>./ex.sh
It... (6 Replies)
Discussion started by: DreamWarrior
6 Replies
9. Solaris
Hello everyone.
I beg your guys pardon please.
I try to ls -al in many path/directories. So, I put the code in text file which look like below;
ls -al /
ls -al /etc
ls -al /etc/default
...
however, when I paste it to Solaris over SecureCRT, it seems the code was escaped from "-" to... (0 Replies)
Discussion started by: Smith
0 Replies
10. Shell Programming and Scripting
Hi there,
I have a strange problem and I cannot figure it out what I am doing wrong here.
Let me try to picture it.
In principle it is prety straight forward, but something odd is happening.
Here is part of the input file snmp_alm.cfg:
... (2 Replies)
Discussion started by: ejdv
2 Replies
SHUTDOWN(2) BSD System Calls Manual SHUTDOWN(2)
NAME
shutdown -- disable sends and/or receives on a socket
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/types.h>
#include <sys/socket.h>
int
shutdown(int s, int how);
DESCRIPTION
The shutdown() system call disables sends or receives on a socket. The how argument specifies the type of shutdown. Possible values are:
SHUT_RD Further receives will be disallowed.
SHUT_WR Further sends will be disallowed. This may cause actions specific to the protocol family of the socket s to happen; see
IMPLEMENTATION NOTES.
SHUT_RDWR Further sends and receives will be disallowed. Implies SHUT_WR.
If the file descriptor s is associated with a SOCK_STREAM socket, all or part of the full-duplex connection will be shut down.
IMPLEMENTATION NOTES
The following protocol specific actions apply to the use of SHUT_WR (and potentially also SHUT_RDWR), based on the properties of the socket
associated with the file descriptor s.
Domain Type Protocol Return value and action
PF_INET SOCK_DGRAM IPPROTO_SCTP Return -1. The global variable errno will be set to EOPNOTSUPP.
PF_INET SOCK_DGRAM IPPROTO_UDP Return 0. ICMP messages will not be generated.
PF_INET SOCK_STREAM IPPROTO_SCTP Return 0. Send queued data and tear down association.
PF_INET SOCK_STREAM IPPROTO_TCP Return 0. Send queued data, wait for ACK, then send FIN.
PF_INET6 SOCK_DGRAM IPPROTO_SCTP Return -1. The global variable errno will be set to EOPNOTSUPP.
PF_INET6 SOCK_DGRAM IPPROTO_UDP Return 0. ICMP messages will not be generated.
PF_INET6 SOCK_STREAM IPPROTO_SCTP Return 0. Send queued data and tear down association.
PF_INET6 SOCK_STREAM IPPROTO_TCP Return 0. Send queued data, wait for ACK, then send FIN.
RETURN VALUES
The shutdown() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi-
cate the error.
ERRORS
The shutdown() system call fails if:
[EBADF] The s argument is not a valid file descriptor.
[EINVAL] The how argument is invalid.
[EOPNOTSUPP] The socket associated with the file descriptor s does not support this operation.
[ENOTCONN] The s argument specifies a SOCK_STREAM socket which is not connected.
[ENOTSOCK] The s argument does not refer to a socket.
SEE ALSO
connect(2), socket(2), inet(4), inet6(4)
STANDARDS
The shutdown() system call is expected to comply with IEEE Std 1003.1g-2000 (``POSIX.1''), when finalized.
HISTORY
The shutdown() system call appeared in 4.2BSD. The SHUT_RD, SHUT_WR, and SHUT_RDWR constants appeared in IEEE Std 1003.1g-2000
(``POSIX.1'').
AUTHORS
This manual page was updated by Bruce M. Simpson <bms@FreeBSD.org> to reflect how shutdown() behaves with PF_INET and PF_INET6 sockets.
BUGS
The ICMP ``port unreachable'' message should be generated in response to datagrams received on a local port to which s is bound after
shutdown() is called.
BSD
March 5, 2007 BSD
