Re: Script typeface.

pe...@easthope.ca wrote: > From: debian-u...@howorth.org.uk > Date: Wed, 30 Oct 2024 22:06:02 + > > Have you looked at https://elementor.com/blog/handwriting-fonts/ ? > > Looked since you mentioned. The heading I cited appears to be > in Pacifico font. > > Elementor is charging us

Re: Script typeface.

From: debian-u...@howorth.org.uk Date: Wed, 30 Oct 2024 22:06:02 + > Have you looked at https://elementor.com/blog/handwriting-fonts/ ? Looked since you mentioned. The heading I cited appears to be in Pacifico font. Elementor is charging us 50+ dollars/yr. I don't see a mention of

Re: Script typeface.

From: Ash Joubert Date: Thu, 31 Oct 2024 12:26:39 +1300 > Try filtering Google Fonts by Calligraphy / > Handwritten. That gives 81 fonts to consider. Good, thx, ... P. -- VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:Pet

Re: Script typeface.

pe...@easthope.ca wrote: > Hi, > > Apparently the page here was constructed using something called > Elementor. https://www.friendsofthegulfislands.ca > > The heading is in a script style of typeface. > > I'm interested to find a free, open source replacment font

Script typeface.

Hi, Apparently the page here was constructed using something called Elementor. https://www.friendsofthegulfislands.ca The heading is in a script style of typeface. I'm interested to find a free, open source replacment font. Not necessarily the same in appearance but aesthetically approp

Re: Cleanup in a bash script

On Thu, Oct 03, 2024 at 03:19:09PM +0300, Anssi Saari wrote: > writes: > > > What actually happens seems completely different to me: the shell > > gets the EPIPE from the dying tee before it can see the EINTR, right? > > That depends. tee -i will ignore SIGINT but ./s

Re: Cleanup in a bash script

writes: > What actually happens seems completely different to me: the shell > gets the EPIPE from the dying tee before it can see the EINTR, right? That depends. tee -i will ignore SIGINT but ./script gets it. So it can keep writing in the pipe, from the script proper or its SIGINT handl

Re: Cleanup in a bash script

Greg Wooledge (12024-10-02): > In that case, there are THREE foreground processes which receive a SIGINT: > > * The interactive shell, which ignores it, because interactive shells >always ignore SIGINT. You are very right on the rest, but this is a mistake: the interactive shell is not in th

Re: Cleanup in a bash script

On Wed, Oct 02, 2024 at 08:17:34AM -0400, Greg Wooledge wrote: [...] Thanks for your (as always) very exhaustive description. > What I'm mostly trying to convey here, though, is that signals do not > *propagate* from one process to another in any kind of automatic way. That's more or less what

Re: Cleanup in a bash script

On Wed, Oct 02, 2024 at 13:59:04 +0200, to...@tuxteam.de wrote: > On Wed, Oct 02, 2024 at 02:43:11PM +0300, Anssi Saari wrote: > > Running ./script |& tee -i log works as expected. The script gets the > > INT signal and cleans up. > > Understood. > > > To me,

Re: Cleanup in a bash script

bvious solution to > Tim's problem, as he wrote: > > QUOTE > ./script |& tee log > > and now it doesn't clean up if I it." > END QUOTE > > Running ./script |& tee -i log works as expected. The script gets the > INT signal and cleans up. U

Re: Cleanup in a bash script

on trying to debug something else, I wanted to run it like this: >> >> > >> >> > ./script |& tee log >> >> > >> >> > and now it doesn't clean up if I it. >> >> >> >> Just a point here about tee since I didn't see an

Re: Cleanup in a bash script

On Tue, Oct 01, 2024 at 01:53:26PM +0300, Anssi Saari wrote: > Greg Wooledge writes: > > > On Mon, Sep 30, 2024 at 14:08:19 +0300, Anssi Saari wrote: > >> Tim Woodall writes: > >> > >> > However on trying to debug something else, I wanted to run it li

Re: Cleanup in a bash script

Greg Wooledge writes: > On Mon, Sep 30, 2024 at 14:08:19 +0300, Anssi Saari wrote: >> Tim Woodall writes: >> >> > However on trying to debug something else, I wanted to run it like this: >> > >> > ./script |& tee log >> > >> >

Re: Cleanup in a bash script

ing? In this particular case it's almost certain that the tee program will have gone away before the bash script calls the exit handler. That last sentence seems _very_ relevant here. If the other end of the pipe is gone, then the shell builtin `echo` probably fails with SIGPIPE/EPIPE. So will

Re: Cleanup in a bash script

On Mon, Sep 30, 2024 at 14:08:19 +0300, Anssi Saari wrote: > Tim Woodall writes: > > > However on trying to debug something else, I wanted to run it like this: > > > > ./script |& tee log > > > > and now it doesn't clean up if I it. > > Ju

Re: Cleanup in a bash script

Tim Woodall writes: > However on trying to debug something else, I wanted to run it like this: > > ./script |& tee log > > and now it doesn't clean up if I it. Just a point here about tee since I didn't see anyone else mention it. tee has had the -i option to igno

Re: Cleanup in a bash script

g? > > In this particular case it's almost certain that the tee program will > have gone away before the bash script calls the exit handler. That last sentence seems _very_ relevant here. If the other end of the pipe is gone, then the shell builtin `echo` probably fails with SIGPIPE

Re: Cleanup in a bash script

On Sat, 28 Sep 2024, Greg Wooledge wrote: On Sat, Sep 28, 2024 at 14:53:10 +0100, Tim Woodall wrote: Is there a way in bash to guarantee that a trap gets called for cleanup in a script? #!/bin/bash trap cleanup EXIT cleanup() { ... } This works in bash -- i.e., it calls the cleanup

Re: Cleanup in a bash script

On Sat, Sep 28, 2024 at 15:17:47 +0100, Alain D D Williams wrote: > On Sat, Sep 28, 2024 at 10:13:59AM -0400, Greg Wooledge wrote: > > On Sat, Sep 28, 2024 at 14:53:10 +0100, Tim Woodall wrote: > > > Is there a way in bash to guarantee that a trap gets called for cleanup

Re: Cleanup in a bash script

On Sat, Sep 28, 2024 at 10:13:59AM -0400, Greg Wooledge wrote: > On Sat, Sep 28, 2024 at 14:53:10 +0100, Tim Woodall wrote: > > Is there a way in bash to guarantee that a trap gets called for cleanup > > in a script? > > #!/bin/bash > trap cleanup EXIT > cleanup() { &g

Re: Cleanup in a bash script

On Sat, Sep 28, 2024 at 14:53:10 +0100, Tim Woodall wrote: > Is there a way in bash to guarantee that a trap gets called for cleanup > in a script? #!/bin/bash trap cleanup EXIT cleanup() { ... } This works in bash -- i.e., it calls the cleanup function regardless of whether the shell

Re: Cleanup in a bash script

On 9/28/24 15:53, Tim Woodall wrote: Is there a way in bash to guarantee that a trap gets called for cleanup in a script? I have a script that works perfectly normally and cleans up after itself, even if it goes wrong. However on trying to debug something else, I wanted to run it like this

Cleanup in a bash script

Is there a way in bash to guarantee that a trap gets called for cleanup in a script? I have a script that works perfectly normally and cleans up after itself, even if it goes wrong. However on trying to debug something else, I wanted to run it like this: ./script |& tee log and now it doe

Re: OT: Question to shell script

Hans writes: > What I am exactly want to do: > > I have 5 live-build directories. In each I am starting my own script, which > is > setting variables and so on for the individual build and does some other > things (rennamin and copying the resulted ISO and so on). So you&#

Re: OT: Question to shell script

What I am exactly want to do: I have 5 live-build directories. In each I am starting my own script, which is setting variables and so on for the individual build and does some other things (rennamin and copying the resulted ISO and so on). As each build must be started within the live-build

Re: OT: Question to shell script

Am 06.09.2024 um 12:25 schrieb Hans: > Dear list, > > I am stuck with a little problem and know no one, whom I can ask. So I allow > me to ask here. > > I have several directories, and in each directory there is a shell script, > which MUST be started within and from

Re: OT: Question to shell script

cd "$(dirname "$0")" > > https://mywiki.wooledge.org/BashFAQ/028 Ah, got it - $0 is not reliably the location of the running script. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Re: OT: Question to shell script

Andy Smith (12024-09-06): > cd "$(dirname "$0")" … || exit Regards, -- Nicolas George

Re: OT: Question to shell script

On Fri, Sep 06, 2024 at 11:10:16 +, Andy Smith wrote: > Is there a reason not to just make these scripts cd to their own > directory so the caller doesn't have to care? > > cd "$(dirname "$0")" https://mywiki.wooledge.org/BashFAQ/028

Re: OT: Question to shell script

On Fri, Sep 06, 2024 at 12:25:11 +0200, Hans wrote: > I have several directories, and in each directory there is a shell script, > which MUST be started within and from its path. I'm not clear on what "within and from its path" means here, but let's suppose you mean

Re: OT: Question to shell script

Hi, On Fri, Sep 06, 2024 at 12:25:11PM +0200, Hans wrote: > I have several directories, and in each directory there is a shell script, > which MUST be started within and from its path. Is there a reason not to just make these scripts cd to their own directory so the caller doesn't h

OT: Question to shell script

Dear list, I am stuck with a little problem and know no one, whom I can ask. So I allow me to ask here. I have several directories, and in each directory there is a shell script, which MUST be started within and from its path. Now I want to edit a "master-shell-script", which I

Re: How to run automatically a script as soon root login

On Tue, May 14, 2024 at 02:51:17PM +0200, Mario Marietto wrote: > I've installed the Cloudflare gateway on Debian as a vm because I can't do > it directly in FreeBSD. But I want to be covered even when I use FreeBSD. > The script that I wrote forward the Cloudflare "VPN&q

Re: How to run automatically a script as soon root login

I've installed the Cloudflare gateway on Debian as a vm because I can't do it directly in FreeBSD. But I want to be covered even when I use FreeBSD. The script that I wrote forward the Cloudflare "VPN" from Debian to FreeBSD,so from outside my IP will be cloudFlared. On Tu

Re: How to run automatically a script as soon root login

On Tue, May 14, 2024 at 01:10:05PM +0200, Mario Marietto wrote: > Your answer does not help me to understand how to use a "structured > programming / if , while, for, functions" for the specific task that I want > to achieve. What task is that?

Re: How to run automatically a script as soon root login

different way,a modern way, for creating my script ? > Why > > did I feel so comfortable by recreating the 1960s GOTO statement in Bash > ? > > I have absolutely no clue what you're trying to do or why you're trying > to do it, but I *promise* you, whatever you thi

Re: How to run automatically a script as soon root login

On Tue, May 14, 2024 at 08:09:18AM +0200, Mario Marietto wrote: > Nobody can show a different way,a modern way, for creating my script ? Why > did I feel so comfortable by recreating the 1960s GOTO statement in Bash ? I have absolutely no clue what you're trying to do or why you'

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

On Tue, May 14, 2024 at 04:54:26PM +0800, Bret Busby wrote: > > Wasn't sudo echo the name of a pop group? > > :) If it wasn't it should've been one. Cheers -- t signature.asc Description: PGP signature

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

Wasn't sudo echo the name of a pop group? :) Bret Busby Armadale Western Australia (UTC+0800) .

Re: How to run automatically a script as soon root login

On Tue, May 14, 2024 at 08:09:18AM +0200, Mario Marietto wrote: > Nobody can show a different way,a modern way, for creating my script ? Why > did I feel so comfortable by recreating the 1960s GOTO statement in Bash ? I think your style is too alien to most of the people here to make the

Re: How to run automatically a script as soon root login

Nobody can show a different way,a modern way, for creating my script ? Why did I feel so comfortable by recreating the 1960s GOTO statement in Bash ? On Mon, May 13, 2024 at 6:30 PM Will Mengarini wrote: > Nobody has yet applauded this glorious implementation > of the 1960s GOTO statem

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

On Mon, May 13, 2024 at 08:37:16PM +0200, Erwan David wrote: > Le 13/05/2024 à 19:45, Stefan Monnier a écrit : [...] > > % sudo zsh -l > > # echo 1 > /proc/sys/net/ipv4/ip_forward > > # ^D > > logout > > % > > > > 🙂 > > > > > > Stefan > > > > > sudo -i will

Re: How to run automatically a script as soon root login

> > > > > > Sorry, dumb question: Depending of the shell, the user is using > (let's > > > say, he > > > > will use bash), can the script not be added into ~/.bashrc? > > > > > > The context has been snipped out. The context for this was

Re: How to run automatically a script as soon root login

y 13, 2024 at 07:36:07AM +0200, Richard wrote: > > > > > .profile > > > > > > Sorry, dumb question: Depending of the shell, the user is using (let's > > say, he > > > will use bash), can the script not be added into ~/.bashrc? > > > > The

Re: How to run automatically a script as soon root login

file > > > > Sorry, dumb question: Depending of the shell, the user is using (let's > say, he > > will use bash), can the script not be added into ~/.bashrc? > > The context has been snipped out. The context for this was "OP is trying > to run a command when r

Re: How to run automatically a script as soon root login

s say, > he > will use bash), can the script not be added into ~/.bashrc? The context has been snipped out. The context for this was "OP is trying to run a command when root logs in". The method of login was not stated. First responder said ".profile works for every me

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

Le 13/05/2024 à 19:45, Stefan Monnier a écrit : $ su - Password: # echo 1 > /proc/sys/net/ipv4/ip_forward # ^D logout $ I don't need no stinkin' sudo :-) And if you only have `sudo`, but not the root password, of course: % sudo zsh -l # echo 1 > /proc/sys/net/ipv4/ip_forward # ^

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

On Mon, May 13, 2024 at 01:45:40PM -0400, Stefan Monnier wrote: > > $ su - > > Password: > > # echo 1 > /proc/sys/net/ipv4/ip_forward > > # ^D > > logout > > $ > > > > I don't need no stinkin' sudo :-) > > And if you only have `sudo`, but not the root password, of course: > > % sudo zsh -l >

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

> $ su - > Password: > # echo 1 > /proc/sys/net/ipv4/ip_forward > # ^D > logout > $ > > I don't need no stinkin' sudo :-) And if you only have `sudo`, but not the root password, of course: % sudo zsh -l # echo 1 > /proc/sys/net/ipv4/ip_forward # ^D logout % 🙂 Stefan

Re: sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

On 5/13/24 18:52, to...@tuxteam.de wrote: Now share your ideas :-) $ su - Password: # echo 1 > /proc/sys/net/ipv4/ip_forward # ^D logout $ I don't need no stinkin' sudo :-) regards, chris

Re: How to run automatically a script as soon root login

>> If yes, second dumb question: Coiuld it be ANY script or command? >> (also running as non-rootuser, like adding "runuser -u myuser >> command_whatever"). >Root can do this, yes. Or to be more precise, .bashrc (and any file that's read from it like .bash_al

Re: How to run automatically a script as soon root login

I think I have found my way,adding this line to /etc/sudoers : marietto ALL=(ALL) NOPASSWD: /usr/bin/iptables and on the warp script : sudo /usr/bin/iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE On Mon, May 13, 2024 at 3:20 PM wrote: > On Mon, May 13, 2024 at 09:17:31AM -0

sudo echo 1 > /proc/sys/net/ipv4/ip_forward [was: How to run automatically a script as soon root login]

Since this happens so often, I'm trying to offer a recap. As others have noted, the above sudo echo 1 > /proc/sys/net/ipv4/ip_forward won't work, since it runs echo under sudo, but the file opening (that pesky ">") happens in your shell, which is probably running unprivileged (otherwise, what

Re: How to run automatically a script as soon root login

l "$cmd" > exit > } Anyway, Marietto, you've got two typi: > mid : That should be "mid:". > jump foo That should be "jumpto foo". Once you've got your root-login script working, I hope you move on to implementing a complete open-source PL/I compiler.

Re: How to run automatically a script as soon root login

Mario Marietto writes: > There is still a problem. If I login automatically as user and inside > the script I do this : > > sudo iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE > > it asks me for the password (don't know why it didn't before) but I >

Re: How to run automatically a script as soon root login

I don't have those typos in the code. The typo has been to copy the content of the script by hand on the email message. On Mon, May 13, 2024 at 6:30 PM Will Mengarini wrote: > Nobody has yet applauded this glorious implementation > of the 1960s GOTO statement in *Bash*?! > >

Re: How to run automatically a script as soon root login

s say, > he > will use bash), can the script not be added into ~/.bashrc? Yes. Consult your shell's manual. And it will also depend on whether it is considered to be a "login shell". And on a couple of other factors. > If yes, second dumb question: Coiuld it be ANY scri

Re: How to run automatically a script as soon root login

Am Montag, 13. Mai 2024, 13:24:17 CEST schrieb Greg Wooledge: > On Mon, May 13, 2024 at 07:36:07AM +0200, Richard wrote: > > .profile Sorry, dumb question: Depending of the shell, the user is using (let's say, he will use bash), can the script not be added into ~/.bashrc? If ye

Re: How to run automatically a script as soon root login

ll a problem. If I login automatically as user and inside the > script I do this : > > sudo iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE > > it asks me for the password (don't know why it didn't before) but I can't > issue a password,because the script i

Re: How to run automatically a script as soon root login

There is still a problem. If I login automatically as user and inside the script I do this : sudo iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE it asks me for the password (don't know why it didn't before) but I can't issue a password,because the script inside the

Re: How to run automatically a script as soon root login

> You don't need to, but I definitely think he does. 🙂 ^^ [ Oh, bias, when will you leave me alone? ] Stefan

Re: How to run automatically a script as soon root login

d. The same for until and for. Sorry for that,but I'm not an experienced coder. I try to do my best with what I find on the Internet. I can adapt an already good enough solution to fit my needs,but I'm not able to write a script from scratch. It is also true that I found it good because

Re: How to run automatically a script as soon root login

>> > echo 1 > /proc/sys/net/ipv4/ip_forward >> This doesn't sound right. Maybe you should investigate why you're > No need to “investigate”, the answer is obvious: in You don't need to, but I definitely think he does. 🙂 Stefan

Re: How to run automatically a script as soon root login

Mario Marietto (12024-05-13): > The command iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE > doesn't work if invoked as a user,it says "you must be root". So,as > user,the script seems to be working fine like this : > > function jumpto > { >

Re: How to run automatically a script as soon root login

On Mon, May 13, 2024 at 09:17:31AM -0400, Greg Wooledge wrote: > On Mon, May 13, 2024 at 02:03:59PM +0100, Richmond wrote: > > >> sudo xterm -e "echo 1 > hello" > > > Yes, but why did it allow me to delete the file? I was not root > > then. Try it. > > Because you have write permission on the *di

Re: How to run automatically a script as soon root login

Le 13/05/2024 à 15:03, Richmond a écrit : Erwan David writes: Le 13/05/2024 à 14:36, Richmond a écrit : I was experimenting, and found this works: sudo xterm -e "echo 1 > hello" It created a file owned by root. But I found I was able to remove it without being root even though group and wor

Re: How to run automatically a script as soon root login

On Mon, May 13, 2024 at 02:03:59PM +0100, Richmond wrote: > >> sudo xterm -e "echo 1 > hello" > Yes, but why did it allow me to delete the file? I was not root > then. Try it. Because you have write permission on the *directory* that the file is in. Removing (unlinking) a file is an operation th

Re: How to run automatically a script as soon root login

The command iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE doesn't work if invoked as a user,it says "you must be root". So,as user,the script seems to be working fine like this : function jumpto { label=$1 cmd=$(sed -n "/$label:/{:a;n;

Re: How to run automatically a script as soon root login

Richmond (12024-05-13): > sudo bash -c "echo 1 > hello" Use sh for that. Regards, -- Nicolas George

Re: How to run automatically a script as soon root login

Erwan David writes: > Le 13/05/2024 à 14:36, Richmond a écrit : >> I was experimenting, and found this works: >> >> sudo xterm -e "echo 1 > hello" >> >> It created a file owned by root. But I found I was able to remove it >> without being root even though group and world permissions were read >>

Re: How to run automatically a script as soon root login

writes: > On Mon, May 13, 2024 at 01:36:23PM +0100, Richmond wrote: >> I was experimenting, and found this works: >> >> sudo xterm -e "echo 1 > hello" > > That's like slicing your morning baguette with the chainsaw. I do that too. > > But if it works for you... hey :-) > > Cheers This also wo

Re: How to run automatically a script as soon root login

Richmond wrote: > I was experimenting, and found this works: > > sudo xterm -e "echo 1 > hello" > > It created a file owned by root. But I found I was able to remove it > without being root even though group and world permissions were read > only. The owner of a directory can delete any file in

Re: How to run automatically a script as soon root login

On Mon, May 13, 2024 at 02:53:18PM +0200, Nicolas George wrote: > to...@tuxteam.de (12024-05-13): > > That's like slicing your morning baguette with the chainsaw. > > Worse than that, it will only work from an X11 environment. Certainly > not at boot. The analogy to that would be that not many ki

Re: How to run automatically a script as soon root login

to...@tuxteam.de (12024-05-13): > That's like slicing your morning baguette with the chainsaw. Worse than that, it will only work from an X11 environment. Certainly not at boot. Regards, -- Nicolas George

Re: How to run automatically a script as soon root login

On Mon, May 13, 2024 at 01:36:23PM +0100, Richmond wrote: > I was experimenting, and found this works: > > sudo xterm -e "echo 1 > hello" That's like slicing your morning baguette with the chainsaw. But if it works for you... hey :-) Cheers -- t signature.asc Description: PGP signature

Re: How to run automatically a script as soon root login

Le 13/05/2024 à 14:36, Richmond a écrit : I was experimenting, and found this works: sudo xterm -e "echo 1 > hello" It created a file owned by root. But I found I was able to remove it without being root even though group and world permissions were read only. thats because sudo exceutes a xt

Re: How to run automatically a script as soon root login

I was experimenting, and found this works: sudo xterm -e "echo 1 > hello" It created a file owned by root. But I found I was able to remove it without being root even though group and world permissions were read only.

Re: How to run automatically a script as soon root login

Dan Ritter (12024-05-13): > Mario Marietto wrote:> If you run > > sudo echo 1 > /proc/sys/net/ipv4/ip_forward > > then the shell you are running it from will run "sudo echo 1" > and then try to put the output in that file. Other way around: the shell first tries to redirect the output to the fi

Re: How to run automatically a script as soon root login

a normal user that can use sudo. If you run sudo echo 1 > /proc/sys/net/ipv4/ip_forward then the shell you are running it from will run "sudo echo 1" and then try to put the output in that file. That fails because the running process is owned by you, not root. If you put the echo

Re: How to run automatically a script as soon root login

Stefan Monnier (12024-05-13): > > echo 1 > /proc/sys/net/ipv4/ip_forward > > > > work only if I'm root. It does not work using sudo. > This doesn't sound right. Maybe you should investigate why you're > seeing this behavior, rather than work around the problem. > > `sudo` *is* root. No need to “

Re: How to run automatically a script as soon root login

> echo 1 > /proc/sys/net/ipv4/ip_forward > > work only if I'm root. It does not work using sudo. This doesn't sound right. Maybe you should investigate why you're seeing this behavior, rather than work around the problem. `sudo` *is* root. Stefan

Re: How to run automatically a script as soon root login

On Mon, May 13, 2024 at 01:48:25PM +0200, Mario Marietto wrote: > I wouldn't to login as root automatically,but I've realized that this > command : > > echo 1 > /proc/sys/net/ipv4/ip_forward > > work only if I'm root. It does not work using sudo. So,in the end I've > chosen to be root instead of

Re: How to run automatically a script as soon root login

Le 13/05/2024 à 13:48, Mario Marietto a écrit : --> If they only want this thing to happen when root logs in directly on a console or ssh, then .profile may indeed be the correct answer. Yes,I don't need to run xorg and a desktop environment,since warp-cli disconnect and warp-cli connect do no

Re: How to run automatically a script as soon root login

--> If they only want this thing to happen when root logs in directly on a console or ssh, then .profile may indeed be the correct answer. Yes,I don't need to run xorg and a desktop environment,since warp-cli disconnect and warp-cli connect do not require them. I wouldn't to login as root automati

Re: How to run automatically a script as soon root login

Hello to everyone, Richard,thanks. I've launched the script inside the .profile file that's inside the root folder and it worked. Thank you. Plan B : From time to time the cloudflare connection stops working,so there is the needing to repeat these commands : warp-cli disconnect warp-c

Re: How to run automatically a script as soon root login

On Mon, May 13, 2024 at 07:36:07AM +0200, Richard wrote: > .profile > will always be read as soon as the user logs in, no matter how. Through a > terminal, a GUI, doesn't matter. That's not correct. There are many different GUI login setups where the .profile is never read. That said, since this

Re: How to run automatically a script as soon root login

Should be as easy as executing the script from the .profile of root - that means if "log in as root" actually means root, not just sudo'ing. .profile will always be read as soon as the user logs in, no matter how. Through a terminal, a GUI, doesn't matter. No idea if doing thi

Re: How to run automatically a script as soon root login

On Sun 12/05/2024 at 22:52, Mario Marietto wrote: > I want that the warp script is run everytime root is logged in,not more,not > less. The second half of this seems to do what you want https://stackoverflow.com/a/39024841

How to run automatically a script as soon root login

Hello to everyone. I'm using Debian 12. I'm configuring a little Debian 12 vm with qemu that I will use to forward the cloudflare connection to FreeBD. What I want to do is to run the script below as soon as root has logged in. I've configured the automatic login of root adding

Re: Using a Python script as a login shell

le. Aside from having a practically un-googleable name it is very nice, and does a lot with very little code. So far, so good. But: If I write a Python script with this module, and expose it to the internet via SSH, will hell break loose? So far I've done the following: 1. Put my script

Using a Python script as a login shell

Hello fellow Debianites! I want do do a custom CLI for a project, and I am quite happy with the Python cmd module. Aside from having a practically un-googleable name it is very nice, and does a lot with very little code. So far, so good. But: If I write a Python script with this module, and

Re: script/history

On Mon 05/02/2024 at 00:45, Greg Wooledge wrote: ... > If you're one of these "I want every command I ever run to be in my > shell history, retained forever, and I don't care how much space it > takes" people, then there are web pages out there that can help you. > I don't follow that philosophy m

Re: script/history

(Re)posting the below as requested, and can confirm history -r seems to have the desired effect. Thanks. - Original message - From: Will Mengarini To: Gareth Evans Cc: debian-user@lists.debian.org Subject: Re: script/history Date: Monday, 5 February 2024 01:02 * Gareth Evans [24

Re: script/history

* Gareth Evans [24-02/04=Su 09:46 +]: > Re the script command, does anyone know of a way to make > commands run during a script session appear in bash history too? You want the 'history -r' command, "explained" by `help history`. After you end the script, you&#x

Re: script/history

On Mon, Feb 05, 2024 at 12:28:38AM +, Gareth Evans wrote: > I was trying to view the history of commands run during a script session. > > user@qwerty:~$ script foo > Script started, output log file is 'foo'. > user@qwerty:~$ date > Mon 5 Feb 00:21:16 GMT 2024

Re: script/history

y, the 4.4BSD csh)". It > appears that bash supports it syntactically, but not its semantics. > I'm not sure why you mentioned this shell detail specifically. I was just highlighting a way to see if behaviour differs between bash "proper" and script running in bash.

Re: script/history

On Sun 04/02/2024 at 17:33, Greg Wooledge wrote: ... > The script(1) utility has NOTHING to do with running ordinary shell > scripts. I understand that. I was trying to view the history of commands run during a script session. user@qwerty:~$ script foo Script started, output log file i

Re: script/history

On Sun, Feb 04, 2024 at 01:45:27PM -0600, David Wright wrote: > SCRIPT(1) User Commands SCRIPT(1) > [ … ] > HISTORY > The script command appeared in 3.0BSD. > > I have no idea why "the history mechanism" is even mentioned >

Re: script/history

On Sun 04 Feb 2024 at 16:01:29 (+), Gareth Evans wrote: > On Sun 04/02/2024 at 13:24, Max Nikulin wrote: > > On 04/02/2024 16:46, Gareth Evans wrote: > >> Re the script command, does anyone know of a way [ … ] > > [...] > >> man script says > >> &

  1   2   3   4   5   6   7   8   9   10   >