Re: Tomcat
by Rahul Sadotra
Hi Michael,
--- Michael Folin <michael.folin(a)donator.se> wrote:
> how do I install Tomcat i fedora?
> can't find it during the installation
>
If you mean during the installation of Fedora Core
itself, then I don't think Tomcat is provided with
Fedora Core (please feel free to correct me if I'm
wrong).
This means you will probably need to download Apache
Jakarta Tomcat (either binaries, or the source which
you'll need to build) and install it.
Hope this helps.
All the best,
Rahul
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
2 weeks
SATA optical drives
by David Fletcher
I'm currently running FC5, will probably upgrade to F7 in a couple of months.
Unfortunately my CD/DVD rewriter appears to have died, before it's
even seen a dual layer disk :'(
SATA hard drives run without problems for me, but now that SATA
optical drives are starting to appear in the shops, would it be OK to
buy one of these and get rid of another wide ribbon cable?
Is anybody already running them with Fedora?
Thanks for any advice/experiences.
Dave F
11 months, 2 weeks
Re: cisco ise
by Patrick O'Callaghan
On Tue, 2020-04-28 at 16:45 +0000, david richyad wrote:
> cisco ise helps safeguard your business. It lets you control access throughout your network, see the user and device details, and stop/contain any threats. You can also use it to enforce security policies throughout your network. As a result, it helps prevent any technical issues and strengthens your cybersecurity measures. In short, you can manage your network security with more ease. Everything can be handled in one place, as opposed to needing multiple different applications open at once.
>
> https://www.fieldengineer.com/blogs/cisco-ise-deployment-guide
Does this have anything to do with Fedora? Advertising is not
acceptable on this list.
poc
1 year
Apache and umask for document root
by Alex
Hi,
I've set up a virtual host for a joomla website and having some
permissions problems. I've seen numerous configurations online about
how to set umask for the apache user, but none have worked, including
creating a systemd file
(/etc/systemd/system/multi-user.target.wants/httpd.service) with the
following:
[Unit]
Description=The Apache HTTP Server
After=network.target remote-fs.target nss-lookup.target
[Service]
Type=notify
Environment=LANG=C
Umask=0006
ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
ExecReload=/usr/sbin/httpd $OPTIONS -k graceful
# Send SIGWINCH for graceful stop
KillSignal=SIGWINCH
KillMode=mixed
PrivateTmp=true
[Install]
WantedBy=multi-user.target
The problem is that the files are owned by the joomla user, but also
need to have access (both read and write) to be able to modify some
files within the document root.
Does anyone have any suggestions on how to set umask for the apache user?
I'm also interested in recommended permissions settings for the joomla
document root.
Thanks,
Alex
1 year, 10 months
[FC8] ssh and CAC card???
by Todd Denniston
From what I understood, the change to openssh listed in:
rpm -q --changelog openssh |less
as:
"* Wed Jun 20 2007 Tomas Mraz <tmraz(a)redhat.com> - 4.5p1-7
- experimental NSS keys support
- correctly setup context when empty level requested (#234951)
"
was supposed to allow the Common Access Card (CAC) to work with the shipped
Fedora 8 ssh.
As per NSS usual, everything is undocumented, i.e., `ssh-add --help` does not
help at all, and `man ssh-add` points to `ssh-add -s reader`
# ssh-add -s 0
Enter passphrase for smartcard:
SSH_AGENT_FAILURE
Could not add card: 0
# ssh-add -s 1
Enter passphrase for smartcard:
SSH_AGENT_FAILURE
Could not add card: 1
So does anyone know how to use the possible functionality, or are we reduced
to reading the source?
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
1 year, 10 months
Changing date with procmail
by Michael A. Peters
Anyone know of a procmail recipe to change the date on incoming
messages?
If the date is in the future by more than 24 hours - I'd like to just
change it to the current date.
If the date is in the past by more than two weeks - I'd like to just
change it to the current date.
I'd like to do it in procmail - if someone knows how.
I've done some searching, still have some to do.
Found some stuff on extracting the date, but not on modifying it if
necessary.
1 year, 12 months
Re: ssh infested by systemd.resolved
by Jonathan Billings
On Apr 23, 2022, at 22:36, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
> As far as I know there isn't really a technical argument for systemd
> or any particular systemd.* on Fedora workstations. The various
> traditional inits and daemons work fine in that environment.[1]
There are several features in systemd that directly benefit the desktop.
1.) systemd service dependencies can ensure that the desktop environment doesn’t launch until all dependencies are met. The side benefit of this is that with parallel startup of services, the desktop launches faster, but it also launches with all the services it needs.
2.) systemd-logind helps contain desktop processes in cgroups, meaning that if you want it to, it will terminate all user processes *for that session* when it logs out. This is a huge thing for the enterprise desktop environments. For example, I managed engineering desktops and there was a particularly finicky circuit designer that loved to leave background processes that would survive logouts, and if another user logged in it would interfere.
But this process management also introduced resource management per-user session, so you could ensure a single user couldn’t abuse the system. This was also important to me, since we had multi-user systems running graphical sessions via VNC, and we wanted to make sure one user didn’t overwhelm the system.
3.) systemd now launches your GUI. You have your own private systemd --user running every time you log in. This process launches services and apps, maintains your environment, and can run other systemd units such as timers. This gives you a similar interface to system services, scoped just to your account. Since there’s only one user systemd per user, you can launch a process that can be used and managed by both the graphical login and a ssh session. (This is actually annoying to me, since it means stuff like Kerberos and AFS works differently than it used to)
4.) the desktop session output and error are captured in the journal. Previously init systems had user console lost to the user. There was some attempt to capture the X logs and the gnome session, but in systemd each user unit can be individually examined with journalctl.
This is just stuff off the top of my head. While I do agree that there has been a lot of focus on server with systemd, a lot of cool things (like unit templating) were introduced because of systemd on workstations. Don’t forget that nearly all the common benefits of systemd also help desktops, because at its core, it’s the core init system to launch the OS.
--
Jonathan Billings
2 years
Connecting to printer on Windows 10 System
by Robert McBroom
I have a HP Envy 5530 printer on usb connection to a Windows 10 system.
KDE printer settings seems to find it with a smb URI.
smb:///%2F192.168.1.100%2FHPENVY5530
Keeps asking for a user and password but doesn't accept local users or
users on the remote machine.
An attempt to print a test page fails with a CIFS unable to connect
error NT_STATUS_NOT_FOUND. The setting window is not responsive to any
mouse clicks. Other windows systems print with no problems
What am I missing on getting access?
2 years