07-23-2018
Hi,
You must not give self in super().__init__(self,value).
So super().__init__(value).
This User Gave Thanks to disedorgue For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello everyone, can somebody tell me what is wrong with this code:
while true
do
java myTime > myTime.log
sleep 60
done
I get the following error:
./myTime: Syntax error at line 1 : `while' is not matched.
Thanks in advance! (6 Replies)
Discussion started by: Lem2003
6 Replies
2. Shell Programming and Scripting
Hello all,
Can someone tell me why I'm getting an error in the following code:
export return_code="$?"
if then
echo "load_shaw.sas failed."
exit
else
echo "Trigger the next script..."
# /path/to/next/script
fi
I get an error... (3 Replies)
Discussion started by: mmignot
3 Replies
3. Shell Programming and Scripting
I just wanted to assign the filename to a variable
filename="abc"
datestrng=`date +%Y%m%d`
filextn="txt"
"LOCAL_FILE"${i}=${filename}"_"${datestrng}"."${filextn}
echo "LOCAL_FILE"${i}
I get the following error on 2nd last line
ksh: LOCAL_FILE1=abc_20081114.txt: not... (3 Replies)
Discussion started by: mqasim
3 Replies
4. Shell Programming and Scripting
Trying to do a file count on files between a specific date. I entered the following command, but it's not working:
find . -type f \( -newer startdate -a ! -newer enddate \) -exec "ls -l | wc -l" {} \;
lil help? :D (4 Replies)
Discussion started by: bbbngowc
4 Replies
5. UNIX for Dummies Questions & Answers
1) I have the below code in concattxnrecords.sh shell script and it is calling the genericVars.sh shell script which is mentioned as below has some code inside it which would intialize some variables in it, now my question is will this shell script would inherit those variable definitions or not... (3 Replies)
Discussion started by: Ariean
3 Replies
6. Shell Programming and Scripting
my script is
#!/usr/bin/env python
import datetime
import subprocess
import sys
import os
import signal
from time import sleep
def runForAWhile(cmd, secs=10):
print("running %s" % cmd)
timeout = datetime.timedelta(seconds=secs)
print timeout
proc = subprocess.Popen(cmd,... (0 Replies)
Discussion started by: yanglei_fage
0 Replies
7. Programming
whats the use of inheriting with access specifier as private..?
Please specify the answer with a simple example...
Regards
-- Madhu (5 Replies)
Discussion started by: MadhuM
5 Replies
8. Shell Programming and Scripting
Hello, all
Suppose my current directory has 3 files:
file_1 file_2 file_3
I wrote the following codes:
awk 'BEGIN{while("ls"|getline d) {myarray++}}; END{close("ls");for (i in myarray){print i, myarray}}' /dev/null
I expect the output be like:
1 file_1
2 file_2
3 file_3
... (7 Replies)
Discussion started by: littlewenwen
7 Replies
9. Programming
Hi,
In multi-level inheritance:
class A {
public:
void fun() { cout << "A" << endl; }
};
class B : public A {
public:
void fun() { cout << "A" << endl; }
};
class C : public B { };
int main() {
C c;
c.fun(); // Ans: A
} (1 Reply)
Discussion started by: royalibrahim
1 Replies
10. Shell Programming and Scripting
All,
I have a basic buzz program written in python with return function. If i change return with print,it works fine but i want to know whats wrong with return statement.Can anyone help me whats wrong with this
#!/usr/bin/python
def div4and6(s,e):
for i in range(s,e+1):
if... (5 Replies)
Discussion started by: oky
5 Replies
LEARN ABOUT MOJAVE
chflags
CHFLAGS(1) BSD General Commands Manual CHFLAGS(1)
NAME
chflags -- change file flags
SYNOPSIS
chflags [-fhv] [-R [-H | -L | -P]] flags file ...
DESCRIPTION
The chflags utility modifies the file flags of the listed files as specified by the flags operand.
The options are as follows:
-f Do not display a diagnostic message if chflags could not modify the flags for file, nor modify the exit status to reflect such fail-
ures.
-H If the -R option is specified, symbolic links on the command line are followed. (Symbolic links encountered in the tree traversal
are not followed.)
-h If the file is a symbolic link, change the file flags of the link itself rather than the file to which it points.
-L If the -R option is specified, all symbolic links are followed.
-P If the -R option is specified, no symbolic links are followed. This is the default.
-R Change the file flags for the file hierarchies rooted in the files instead of just the files themselves.
-v Cause chflags to be verbose, showing filenames as the flags are modified. If the -v option is specified more than once, the old and
new flags of the file will also be printed, in octal notation.
The flags are specified as an octal number or a comma separated list of keywords. The following keywords are currently defined:
arch, archived
set the archived flag (super-user only)
opaque set the opaque flag (owner or super-user only). [Directory is opaque when viewed through a union mount]
nodump set the nodump flag (owner or super-user only)
sappnd, sappend
set the system append-only flag (super-user only)
schg, schange, simmutable
set the system immutable flag (super-user only)
uappnd, uappend
set the user append-only flag (owner or super-user only)
uchg, uchange, uimmutable
set the user immutable flag (owner or super-user only)
hidden set the hidden flag [Hide item from GUI]
As discussed in chflags(2), the sappnd and schg flags may only be unset when the system is in single-user mode.
Putting the letters ``no'' before or removing the letters ``no'' from a keyword causes the flag to be cleared. For example:
nouchg clear the user immutable flag (owner or super-user only)
dump clear the nodump flag (owner or super-user only)
Unless the -H or -L options are given, chflags on a symbolic link always succeeds and has no effect. The -H, -L and -P options are ignored
unless the -R option is specified. In addition, these options override each other and the command's actions are determined by the last one
specified.
You can use "ls -lO" to see the flags of existing files.
EXIT STATUS
The chflags utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
ls(1), chflags(2), stat(2), fts(3), symlink(7)
HISTORY
The chflags command first appeared in 4.4BSD.
BUGS
Only a limited number of utilities are chflags aware. Some of these tools include ls(1), cp(1), find(1), install(1), dump(8), and
restore(8). In particular a tool which is not currently chflags aware is the pax(1) utility.
BSD
March 3, 2006 BSD